>2014-10-19 15:18 GMT+02:00 Thiago H de Paula Figueiredo :
>Awesome example, Arve! Thanks for sharing!
:-)
> On Sat, 18 Oct 2014 13:32:08 -0300, Arve Klev wrote:
>
> This could be done in a much simpler way today, I think.
>>
>> I'm using Tapestry 5.4-beta-22 and only the libraries shipped by
Thanks I'll give this a shot with some accordion js stuff that isn't
working.
Awesome example, Arve! Thanks for sharing!
On Sat, 18 Oct 2014 13:32:08 -0300, Arve Klev wrote:
This could be done in a much simpler way today, I think.
I'm using Tapestry 5.4-beta-22 and only the libraries shipped by
Tapestry (Bootstrap, etc.) - love it.
To use Bootstraps popover.js, a compo
This could be done in a much simpler way today, I think.
I'm using Tapestry 5.4-beta-22 and only the libraries shipped by
Tapestry (Bootstrap, etc.) - love it.
To use Bootstraps popover.js, a component we must initialize ourself, I
only need to do this:
In my Layout component (include the modules
Since 5.4-alpha-15 , tapestry use Bootstrap 3.x.
https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=tree;h=f43e87abf9b77f08b99e90aa22b6d54f20ce7bd1;hb=bb23cdc21f68a655f8f2c24bb8c2c2ce5369ca12
http://getbootstrap.com/
http://getbootstrap.com/2.3.2/
5.4-beta-6:
Bootstrap 3.0.3
https://g
Check out the tapestry-webresources test sources/resources. They have an
example of how to use a bootstrap placed in webapp context.
That should be a good starting point for both context-based resources and a
bootstrap in a non-default location.
--
Chris
On Tue, May 27, 2014 at 6:33 PM, Ilya O
In fact, only clearing the browser cache helped to solve my problem -
modules started working after that.
Still everything is pretty messed up:
- context-based resources are not loaded.
- trying to point Bootstrap root to non-default location results in "cannot
load module" errors
etc etc
But t
>From the previous posts it seems that I have already completed all the
necessary steps to get jQuery infrastructure working. But it doesn't.
I just don't have an idea (yet) what to try next.
On Tue, May 27, 2014 at 1:28 PM, Chris Poulsen wrote:
> Start by getting the jquery infrastructure work
Start by getting the jquery infrastructure working. Verify that your module
is being loaded etc.
On Tue, May 27, 2014 at 11:08 AM, Ilya Obshadko wrote:
> Here's my version of contributeApplicationDefaults():
>
> public static void contributeApplicationDefaults (
> MappedConfiguration configu
Here's my version of contributeApplicationDefaults():
public static void contributeApplicationDefaults (
MappedConfiguration configuration ) {
configuration.add ( SymbolConstants.
JAVASCRIPT_INFRASTRUCTURE_PROVIDER, "jquery" );
configuration.add ( SymbolConstants.SUPPORTED_LO
Hi,
The dom module is the one distinguishing between jquery and prototype.
The code you posted belongs in the prototype version, the jquery one is
different...
So it seems that you are not using the jquery infrastructure.
We use the following setting to enable it:
@Contribute( SymbolProvid
So this obviously happens inside t5/core/console initialization.
This is a code fragment in dom.js causing the error:
ElementWrapper.prototype.attr = function(name, value) {
var attributeName, current;
if (_.isObject(name)) {
for (attributeName in name) {
I tried both methods suggested, but page load still produces the same
error.
Then I have turned off all of my custom application JS, by commenting out
@Import, javaScriptSupport.addScript() and
javaScriptSupport.addInitializerCall().
That didn't help either.
I still have this stack trace in brows
Thanks everyone, that's totally makes sense.
On Tue, May 27, 2014 at 7:56 AM, Geoff Callender <
geoff.callender.jumpst...@gmail.com> wrote:
> Hang on - with T5.4 beta-3 I'm pretty sure I'm not doing any of that!
> bootstrap.css and bootstrap.js are drawn in automatically as part of T5's
> core.
that could be so Geoff.
maybe the only advantage to doing it my way is you can switch up bootstrap
versions beyond what tapestry is baking in.
On Mon, May 26, 2014 at 9:56 PM, Geoff Callender <
geoff.callender.jumpst...@gmail.com> wrote:
> Hang on - with T5.4 beta-3 I'm pretty sure I'm not doing
Hang on - with T5.4 beta-3 I'm pretty sure I'm not doing any of that!
bootstrap.css and bootstrap.js are drawn in automatically as part of T5's core.
To use a bootstrap module in your page, try this sort of thing:
void afterRender() {
javaScriptSupport.require("bootstrap/
1 other thing, you will have to Import the bootstrap.js into your ui class
to get it all working.
@Import(library = {"context:bootstrap/js/bootstrap.js"})
public class Index {
On Mon, May 26, 2014 at 4:59 PM, Jon Williams
wrote:
> it's easy to custom setup Tapestry 5.4 to the latest bootstrap v
it's easy to custom setup Tapestry 5.4 to the latest bootstrap version,
with all the widgets.
make the contribution to the environment like so:
configuration.add(SymbolConstants.BOOTSTRAP_ROOT, "context:bootstrap");
then, make a bootstrap distro directory in your webapp context. then put a
a ful
On Mon, 26 May 2014 16:46:27 -0300, Ilya Obshadko
wrote:
I did. Still got the same error.
Tapestry doesn't include the full Bootstrap set of .js files, so you'll
need to import yourself. The Tapestry out-of-the-box Bootstrap offerings
right now are focused on the CSS side, not on the wi
I did. Still got the same error.
On Mon, May 26, 2014 at 10:25 PM, Lance Java wrote:
> Have you swapped the infrastructure provider from prototype to jquery?
>
> Details here:
> https://github.com/bobharner/blog/wiki/Jumping-Into-Tapestry-5.4-Alpha-3
> On 26 May 2014 18:00, "Ilya Obshadko" wro
Have you swapped the infrastructure provider from prototype to jquery?
Details here:
https://github.com/bobharner/blog/wiki/Jumping-Into-Tapestry-5.4-Alpha-3
On 26 May 2014 18:00, "Ilya Obshadko" wrote:
> Turns out I've got "Uncaught TypeError: undefined is not a function" in
> dom.js, line 134
Turns out I've got "Uncaught TypeError: undefined is not a function" in
dom.js, line 134. Don't have any idea where it might come from.
On Mon, May 26, 2014 at 8:26 PM, Ilya Obshadko wrote:
> I've just started migrating from 5.3 to 5.4-beta3. My application already
> heavily relies on Bootstrap
I've just started migrating from 5.3 to 5.4-beta3. My application already
heavily relies on Bootstrap and jQuery. Previously I was using Bootstrap
version 2.3.2, so that's a good time to upgrade Bootstrap as well.
Could someone clarify this for me: Tapestry 5.4 distribution already
contains everyt
23 matches
Mail list logo
