Re: [web2py] IMPORTANT: web2py 2.6.0-development

@testers, please upgrade to trunk. A few changes went in that needs to be tested as well. -- --- 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 web2py+unsubscr.

Re: [web2py] IMPORTANT: web2py 2.6.0-development

I "web2py_framework.js" part of the framework is a good idea. We could have a way to access it like this in a view {{=web2py_js(version='1.0', embed=True)}} -> expanded inline {{=web2py_js(version='1.0', embed=False)}} -> a proper url is generated so that it's content can be fetched in parallel

Re: [web2py] IMPORTANT: web2py 2.6.0-development

Maybe just a check sum on file that should be update after an upgrade could allow to display a message in admin and maybe if the files to be updated have the sum of one of the precedent file mean that the user has didn't change anything those file could be overwritten whitout issue... I would prefe

Re: [web2py] IMPORTANT: web2py 2.6.0-development

We could also minify it so people would be nuts to try to change it. :) On Thu, Jun 27, 2013 at 9:42 AM, Jason (spot) Brower wrote: > I wonder if we should have a comment in the file that they shouldn't > change this file as it will be overwritten. > > > > On Thu, Jun 27, 2013 at 9:38 AM, Massi

Re: [web2py] IMPORTANT: web2py 2.6.0-development

I wonder if we should have a comment in the file that they shouldn't change this file as it will be overwritten. On Thu, Jun 27, 2013 at 9:38 AM, Massimo Di Pierro < massimo.dipie...@gmail.com> wrote: > The problem is that an old app can be installed after an upgrade and it > would not work bec

Re: [web2py] IMPORTANT: web2py 2.6.0-development

The problem is that an old app can be installed after an upgrade and it would not work because it would still come with the old web2py.js. I do not think web2py.js can be update automatically nor it should. On Wednesday, 26 June 2013 14:35:05 UTC-5, LightDot wrote: > > +1 for considering web2p

Re: [web2py] IMPORTANT: web2py 2.6.0-development

just to confirm, ANY javascript piece of code relying on web2py.js functions will still work as intended. At the end of the new web2py.js there is a "compatibility layer" that remaps old function names to the new ones. If someone added his own function, e.g. at the end of "old" web2py.js just

Re: [web2py] IMPORTANT: web2py 2.6.0-development

It sounds good. On Wed, Jun 26, 2013 at 6:04 PM, villas wrote: > I was just thinking that some users might have their own functions mixed > together with web2py functions in web2py.js and might not wish to extricate > their work and save it elsewhere. > > To overcome that, make a completely diff

Re: [web2py] IMPORTANT: web2py 2.6.0-development

I was just thinking that some users might have their own functions mixed together with web2py functions in web2py.js and might not wish to extricate their work and save it elsewhere. To overcome that, make a completely different file to be the framework file. I suggested web2py_framework.js b

Re: [web2py] IMPORTANT: web2py 2.6.0-development

> How about extending this definition and requirement to appadmin..? > I don't think any framework functionality depends on appadmin, so you should be able to keep an old appadmin if you like, but in both the documentation and the admin interface, we should include a reminder to update appadm

Re: [web2py] IMPORTANT: web2py 2.6.0-development

+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 u

Re: [web2py] IMPORTANT: web2py 2.6.0-development

+1 On Wed, Jun 26, 2013 at 1:46 PM, Anthony 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 thi

Re: [web2py] IMPORTANT: web2py 2.6.0-development

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-u

Re: [web2py] IMPORTANT: web2py 2.6.0-development

Are you suggested web2py.js should be served by a spacial action and not being part of the applications? On Wednesday, 26 June 2013 10:21:58 UTC-5, villas wrote: > > +1 Anthony > > These days any sophisticated web framework must surely include some JS. > The framework must be able to guarantee

Re: [web2py] IMPORTANT: web2py 2.6.0-development

+1 Anthony These days any sophisticated web framework must surely include some JS. The framework must be able to guarantee which functions will be available client-side. If we accept that at least one JS must be part of the framework, then we can choose whether this should be web2py.js. Perh

Re: [web2py] IMPORTANT: web2py 2.6.0-development

On Wednesday, June 26, 2013 9:19:23 AM UTC-4, Massimo Di Pierro wrote: > That is dangerous. What if people rely on an older version of have edited > it? That's the point. web2py.js is not like the rest of the scaffold (i.e., optional and customizable) -- it interacts with the core framework, s

Re: [web2py] IMPORTANT: web2py 2.6.0-development

On Wednesday, June 26, 2013 3:19:23 PM UTC+2, Massimo Di Pierro wrote: > > Moreover, what if an old app is installed after an upgrade? > > it won't work, plain and simple. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscrib

Re: [web2py] IMPORTANT: web2py 2.6.0-development

That is dangerous. What if people rely on an older version of have edited it? I think it is part of the specs that web2py upgrades do not touch the apps. Moreover, what if an old app is installed after an upgrade? On Wednesday, 26 June 2013 07:10:16 UTC-5, Anthony wrote: > > More generally, we

Re: [web2py] IMPORTANT: web2py 2.6.0-development

More generally, we should probably make it more clear that web2py.js is properly a part of the framework and must be upgraded whenever the framework is upgraded (this could be mentioned here, and maybe a reminder message could be shown in

Re: [web2py] IMPORTANT: web2py 2.6.0-development

ETA is more or less 1 year on this :-P However, yes, it will be promply highlighted (and maybe in the far distant future web2py.js will be overwritten automatically ). On Wednesday, June 26, 2013 1:36:07 PM UTC+2, viniciusban wrote: > > I think this is a note that must be highlighted before re

Re: [web2py] IMPORTANT: web2py 2.6.0-development

I think this is a note that must be highlighted before releasing as stable, right? On Wed, Jun 26, 2013 at 7:14 AM, Massimo DiPierro wrote: > There is a major change upcoming in web2py 2.6 (which can be tested in trunk). > > The change involves a better rewrite of web2py.js agreed upon the develo

Re: [web2py] IMPORTANT: web2py 2.6.0-development

I'm testing Ovidio Marinho Falcao Neto ITJP.NET.BR ovidio...@gmail.com 83 8826 9088 - Oi 83 9336 3782 - Claro Brasil 2013/6/26 Massimo DiPierro > There is a major change upcoming in web2py 2.

[web2py] IMPORTANT: web2py 2.6.0-development

There is a major change upcoming in web2py 2.6 (which can be tested in trunk). The change involves a better rewrite of web2py.js agreed upon the developers and implemented by Niphlod. Because of this change applications which use components will break unless you upgrade the old web2py.js with