You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Bård Magnus Kvalheim <ma...@kvalheim.eu> on 2013/09/23 14:27:46 UTC
T5.4 migration discussions
Hi guys and Howard :)
So I've been taking 5.4 out for a testdrive (alpha 22).
The application is fairly large 150+ pages, 250+ components and mixins.
*Plugins:* Is using tapestry-jquery, t5conduit (less &
coffieescript), tapestry-yuicompressor (with Lenny's workaround)
The plugins are omitted for 5.4. Think I need to make new components to
make up for loss of tapestry-jquery, but otherwise working good.
At this point I haven't gotten much longer than the home page and a couple
of additional pages, but it's looking really good. Great job on that :-)
There's already been a number of posts related to 5.4 so won't repeat on
those, but have a couple of 'new questions' that might deserve some
attention.
*t53-compatibility.js - load early as possible..?*
Great this one exist, but is is possible to have it load earlier..?
Currently it's loaded last of the "@Import'ed" libraries where some make
use of the Tapestry namespace.
I've manually tested to add it to my layout component (to get it higher in
list), and that mostly work, but not on all pages.
So - is it possible to have it loaded as first in list by default?
*Requirejs optimize*
Since requirejs make you write the modules - one pr. file - it can quickly
add up.
Up until now we've made use of stacks to combine files, but guess this
won't work reliably with with requirejs..?
I've seen there is an optimizer for requirejs.
http://requirejs.org/docs/optimization.html
Any plans to use this - or are there other approaches more suitable for
tapestry?
Will probably have additional questions/comments as I work my way through.
But overall very excited about this release..
cheers
Magnus
Re: T5.4 migration discussions
Posted by Howard Lewis Ship <hl...@gmail.com>.
I do find, unscientifically, that the total amount of JavaScript
downloaded, and the total amount running at any given time, is much less in
5.4 than in 5.3. The new "lighter" approach, based on adding top-level
event handlers rather than creating specific controller objects for
specific elements, is the main difference.
On Tue, Sep 24, 2013 at 2:10 PM, Bård Magnus Kvalheim <ma...@kvalheim.eu>wrote:
> Thanks, that sounds good and would go a long way.
>
> Will make me worry less currently moving from stacks to modules - and it
> does seem cleaner..
>
> On Tue, Sep 24, 2013 at 9:13 PM, Howard Lewis Ship <hl...@gmail.com>
> wrote:
>
> > Actually, I hope to extend the stack concept to allow modules to be
> > included in the stack.
> >
> > RequireJS's optimize does a bit more; you specify some module names and
> it
> > figures out the transitive dependencies and builds a single script. That
> > would be great, but I'm not sure I can pull it off.
> >
> >
> > On Tue, Sep 24, 2013 at 12:57 AM, Bård Magnus Kvalheim
> > <ma...@kvalheim.eu>wrote:
> >
> > > Thanks for reply.
> > >
> > > Do the tapestry-jquery guys mentioned their plans for 5.4? The
> > > > include-jQuery-and-**reimplement-everything-in-**jQuery isn't needed
> > > > anymore, but the other parts should still be quite useful in 5.4.
> > > >
> > >
> > > Yes, think so too.
> > > Looks like the plan is to get it updated, but not sure of timelines
> > here..
> > >
> > > >
> > > > *Requirejs optimize*
> > > >>
> > > >> Since requirejs make you write the modules - one pr. file - it can
> > > >> quickly add up.
> > > >> Up until now we've made use of stacks to combine files, but guess
> this
> > > >> won't work reliably with with requirejs..?
> > > >>
> > > >
> > > > I guess nothing should change to stacks and they should keep on
> working
> > > in
> > > > 5.4. I haven't checked that, though.
> > >
> > >
> > > Yes, it does work :-) Apart from the mentioned t5.3 compability which I
> > > think need to be first in list. (Tapestry namespace)
> > > However don't think it will work to 'stack'/combine requirejs modules
> in
> > > current tapestry way.
> > >
> > > (btw - did try to make my javascriptstack depend on core which seems to
> > > help pushing t5.3 compability higher)
> > >
> > > >
> > > >
> > > > I've seen there is an optimizer for requirejs.
> > > >> http://requirejs.org/docs/**optimization.html<
> > > http://requirejs.org/docs/optimization.html>
> > > >> Any plans to use this - or are there other approaches more suitable
> > for
> > > >> tapestry?
> > > >>
> > > >
> > > > I'm not sure this would fit in Tapestry. The optimizer is written for
> > > > Node.js.
> > >
> > > Yes, it might be out of scope for tapestry. There is a Rhino option -
> > > although it is reported to be very slow (perhaps Nashorn can change
> it?)
> > > Have found other efforts like -
> > > https://github.com/mcheely/requirejs-maven-plugin - which could be
> > tested
> > > as well...
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator of Apache Tapestry
> >
> > The source for Tapestry training, mentoring and support. Contact me to
> > learn how I can get you up and productive in Tapestry fast!
> >
> > (971) 678-5210
> > http://howardlewisship.com
> >
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: T5.4 migration discussions
Posted by Bård Magnus Kvalheim <ma...@kvalheim.eu>.
Thanks, that sounds good and would go a long way.
Will make me worry less currently moving from stacks to modules - and it
does seem cleaner..
On Tue, Sep 24, 2013 at 9:13 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> Actually, I hope to extend the stack concept to allow modules to be
> included in the stack.
>
> RequireJS's optimize does a bit more; you specify some module names and it
> figures out the transitive dependencies and builds a single script. That
> would be great, but I'm not sure I can pull it off.
>
>
> On Tue, Sep 24, 2013 at 12:57 AM, Bård Magnus Kvalheim
> <ma...@kvalheim.eu>wrote:
>
> > Thanks for reply.
> >
> > Do the tapestry-jquery guys mentioned their plans for 5.4? The
> > > include-jQuery-and-**reimplement-everything-in-**jQuery isn't needed
> > > anymore, but the other parts should still be quite useful in 5.4.
> > >
> >
> > Yes, think so too.
> > Looks like the plan is to get it updated, but not sure of timelines
> here..
> >
> > >
> > > *Requirejs optimize*
> > >>
> > >> Since requirejs make you write the modules - one pr. file - it can
> > >> quickly add up.
> > >> Up until now we've made use of stacks to combine files, but guess this
> > >> won't work reliably with with requirejs..?
> > >>
> > >
> > > I guess nothing should change to stacks and they should keep on working
> > in
> > > 5.4. I haven't checked that, though.
> >
> >
> > Yes, it does work :-) Apart from the mentioned t5.3 compability which I
> > think need to be first in list. (Tapestry namespace)
> > However don't think it will work to 'stack'/combine requirejs modules in
> > current tapestry way.
> >
> > (btw - did try to make my javascriptstack depend on core which seems to
> > help pushing t5.3 compability higher)
> >
> > >
> > >
> > > I've seen there is an optimizer for requirejs.
> > >> http://requirejs.org/docs/**optimization.html<
> > http://requirejs.org/docs/optimization.html>
> > >> Any plans to use this - or are there other approaches more suitable
> for
> > >> tapestry?
> > >>
> > >
> > > I'm not sure this would fit in Tapestry. The optimizer is written for
> > > Node.js.
> >
> > Yes, it might be out of scope for tapestry. There is a Rhino option -
> > although it is reported to be very slow (perhaps Nashorn can change it?)
> > Have found other efforts like -
> > https://github.com/mcheely/requirejs-maven-plugin - which could be
> tested
> > as well...
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
Re: T5.4 migration discussions
Posted by Howard Lewis Ship <hl...@gmail.com>.
Actually, I hope to extend the stack concept to allow modules to be
included in the stack.
RequireJS's optimize does a bit more; you specify some module names and it
figures out the transitive dependencies and builds a single script. That
would be great, but I'm not sure I can pull it off.
On Tue, Sep 24, 2013 at 12:57 AM, Bård Magnus Kvalheim
<ma...@kvalheim.eu>wrote:
> Thanks for reply.
>
> Do the tapestry-jquery guys mentioned their plans for 5.4? The
> > include-jQuery-and-**reimplement-everything-in-**jQuery isn't needed
> > anymore, but the other parts should still be quite useful in 5.4.
> >
>
> Yes, think so too.
> Looks like the plan is to get it updated, but not sure of timelines here..
>
> >
> > *Requirejs optimize*
> >>
> >> Since requirejs make you write the modules - one pr. file - it can
> >> quickly add up.
> >> Up until now we've made use of stacks to combine files, but guess this
> >> won't work reliably with with requirejs..?
> >>
> >
> > I guess nothing should change to stacks and they should keep on working
> in
> > 5.4. I haven't checked that, though.
>
>
> Yes, it does work :-) Apart from the mentioned t5.3 compability which I
> think need to be first in list. (Tapestry namespace)
> However don't think it will work to 'stack'/combine requirejs modules in
> current tapestry way.
>
> (btw - did try to make my javascriptstack depend on core which seems to
> help pushing t5.3 compability higher)
>
> >
> >
> > I've seen there is an optimizer for requirejs.
> >> http://requirejs.org/docs/**optimization.html<
> http://requirejs.org/docs/optimization.html>
> >> Any plans to use this - or are there other approaches more suitable for
> >> tapestry?
> >>
> >
> > I'm not sure this would fit in Tapestry. The optimizer is written for
> > Node.js.
>
> Yes, it might be out of scope for tapestry. There is a Rhino option -
> although it is reported to be very slow (perhaps Nashorn can change it?)
> Have found other efforts like -
> https://github.com/mcheely/requirejs-maven-plugin - which could be tested
> as well...
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: T5.4 migration discussions
Posted by Bård Magnus Kvalheim <ma...@kvalheim.eu>.
Thanks for reply.
Do the tapestry-jquery guys mentioned their plans for 5.4? The
> include-jQuery-and-**reimplement-everything-in-**jQuery isn't needed
> anymore, but the other parts should still be quite useful in 5.4.
>
Yes, think so too.
Looks like the plan is to get it updated, but not sure of timelines here..
>
> *Requirejs optimize*
>>
>> Since requirejs make you write the modules - one pr. file - it can
>> quickly add up.
>> Up until now we've made use of stacks to combine files, but guess this
>> won't work reliably with with requirejs..?
>>
>
> I guess nothing should change to stacks and they should keep on working in
> 5.4. I haven't checked that, though.
Yes, it does work :-) Apart from the mentioned t5.3 compability which I
think need to be first in list. (Tapestry namespace)
However don't think it will work to 'stack'/combine requirejs modules in
current tapestry way.
(btw - did try to make my javascriptstack depend on core which seems to
help pushing t5.3 compability higher)
>
>
> I've seen there is an optimizer for requirejs.
>> http://requirejs.org/docs/**optimization.html<http://requirejs.org/docs/optimization.html>
>> Any plans to use this - or are there other approaches more suitable for
>> tapestry?
>>
>
> I'm not sure this would fit in Tapestry. The optimizer is written for
> Node.js.
Yes, it might be out of scope for tapestry. There is a Rhino option -
although it is reported to be very slow (perhaps Nashorn can change it?)
Have found other efforts like -
https://github.com/mcheely/requirejs-maven-plugin - which could be tested
as well...
Re: T5.4 migration discussions
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Mon, 23 Sep 2013 09:27:46 -0300, Bård Magnus Kvalheim
<ma...@kvalheim.eu> wrote:
> Hi guys and Howard :)
Hi!
> So I've been taking 5.4 out for a testdrive (alpha 22).
>
> The application is fairly large 150+ pages, 250+ components and mixins.
> *Plugins:* Is using tapestry-jquery, t5conduit (less &
> coffieescript), tapestry-yuicompressor (with Lenny's workaround)
> The plugins are omitted for 5.4. Think I need to make new components to
> make up for loss of tapestry-jquery, but otherwise working good.
Do the tapestry-jquery guys mentioned their plans for 5.4? The
include-jQuery-and-reimplement-everything-in-jQuery isn't needed anymore,
but the other parts should still be quite useful in 5.4.
> *Requirejs optimize*
> Since requirejs make you write the modules - one pr. file - it can
> quickly add up.
> Up until now we've made use of stacks to combine files, but guess this
> won't work reliably with with requirejs..?
I guess nothing should change to stacks and they should keep on working in
5.4. I haven't checked that, though.
> I've seen there is an optimizer for requirejs.
> http://requirejs.org/docs/optimization.html
> Any plans to use this - or are there other approaches more suitable for
> tapestry?
I'm not sure this would fit in Tapestry. The optimizer is written for
Node.js.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org