+1 for considering web2py.js as a part of web2py framework, so users should be requested to update it along with the framework.
How about extending this definition and requirement to appadmin..? Also - what happens with old apps that have ancient jquery.js? Will new web2py.js cause a chain of upgrades for such users, ie. requires new jquery.js -> requires new 3rd party js libs -> requires code adjustments in the application? I guess now would be a good time to try out old vanilla welcome apps with new web2py/web2py.js... I really hate suggesting such things rather than doing them, but I'm up to ears in a project that's on the deadline so I have very little free time right now :/ Regards, Ales On Wednesday, June 26, 2013 7:00:46 PM UTC+2, viniciusban wrote: > > +1 > > > On Wed, Jun 26, 2013 at 1:46 PM, Anthony <[email protected] <javascript:>> > wrote: > > On Wednesday, June 26, 2013 11:33:59 AM UTC-4, Massimo Di Pierro wrote: > >> > >> Are you suggested web2py.js should be served by a spacial action and > not > >> being part of the applications? > > > > > > Interesting idea. > > > > -- > > > > --- > > You received this message because you are subscribed to the Google > Groups > > "web2py-users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
