Just to poke my uninformed and long-worked-days nose in, I reckon if a bit of sample code that did this caching (and may i chime in, and perhaps allowed for a tapestry configuration symbol to enable/disable this behaviour) were to magically be attached to a jira, then the likelihood of it being considered for 5.5 would sky rocket.
Being somewhat interested in mitigating against breaches and having not given 5.4 a decent look at yet, read this comment (with its tired owners dry tone) with a "grain of salt" I'll just beg my pardon out of this politely and fix a drink :) If the stakeholders of a project wish this behaviour, and no gmaps stuff is ever likely to be needed, could be a nice feature. Cheers Chris On 05/02/2014 7:38 pm, "Kristian Marinkovic" <kristian.marinko...@gmail.com> wrote: > looking at my migrated Tapestry 5.4-beta-2 app i can only see two inline > scripts. The requirejs configuration (shim, ...) and the require call > itself. > > Is it possible to move those into a dynamically generated js instead, > that's included with a script tag? the requirejs config could by cached. > And the require call would be page specific. Should we create a jira > ticket? > > removing the javascriptsupport methods is not a good idea as it breaks > backwards compatibility. on the other hand removing in 5.5 would be nice :) > > g, > Kris > > > > > On Tue, Feb 4, 2014 at 8:52 PM, Thiago H de Paula Figueiredo < > thiag...@gmail.com> wrote: > > > On Tue, 04 Feb 2014 17:45:37 -0200, Christian Köberl < > > tapestry.christian.koeb...@gmail.com> wrote: > > > > 2014-02-04 Lance Java <lance.j...@googlemail.com>: > >> > >>> I happen to be a fan of tapestry's multi-page approach and serverside > >>> markup generation. > >>> > >> Me too - but I think there would be a big chance in 5.4 to clean up > >> the JS stuff and I think inline JS is no good idea. The core > >> components could all be refactored to work without inline JS - like > >> the new DateField (a good example how to do it). > >> > > > > I don't know a politer way of saying this, but I already said that > > Tapestry 5.4 is already doing that at least twice. I'm having a really > > unlucky day. :( > > > > > > -- > > Thiago H. de Paula Figueiredo > > Tapestry, Java and Hibernate consultant and developer > > http://machina.com.br > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > >