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 <hls...@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 > <mag...@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 >
