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, so it 
really belongs to the framework. You shouldn't edit it or rely on an older 
version of it any more than you should edit or rely on an older version of 
one of the gluon modules.

My understanding is that the changes to web2py.js in 2.6.0 will preserve 
backward compatibility of the API for older apps that call ajax(), 
web2py_component(), etc., so apps should only break if they have customized 
web2py.js or if they use some of its non-public functions (behaviors that 
we should discourage going forward).

Anyway, we're already requiring the web2py.js upgrade with 2.6.0 -- why not 
take the opportunity to explicitly make this a general requirement going 
forward rather than being locked in to a frozen version of web2py.js?
 

> I think it is part of the specs that web2py upgrades do not touch the apps.


I think this one file has to be an exception. It doesn't seem feasible to 
have Javascript/ajax integrated with the core framework and yet not require 
that the Javascript be updated along with the framework.

Moreover, what if an old app is installed after an upgrade?


They'll break, but such apps will already break with the planned changes in 
2.6.0.

Anthony

On Wednesday, 26 June 2013 07:10:16 UTC-5, Anthony wrote:
>>
>> 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<http://web2py.com/books/default/chapter/29/14#Upgrading>, 
>> and maybe a reminder message could be shown in admin when its upgrade 
>> button is used).
>>
>> Anthony
>>
>> On Wednesday, June 26, 2013 7:36:07 AM UTC-4, viniciusban wrote:
>>>
>>> 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 
>>> <mdip...@cs.depaul.edu> 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 
>>> developers and implemented by Niphlod. 
>>> > 
>>> > Because of this change  applications which use components will break 
>>> unless you upgrade the old web2py.js with the new one. 
>>> > 
>>> > Anyway, try the latest trunk, check it out, and send us comments. 
>>> > 
>>> > Massimo 
>>> > 
>>> > 
>>> > -- 
>>> > 
>>> > --- 
>>> > 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+un...@googlegroups.com. 
>>> > 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 web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to