On Tuesday, August 7, 2012 9:52:30 PM UTC-4, Massimo Di Pierro wrote: > > This raises an issue. If somebody is using web2py 2.0 with a legacy app > and the old web2py.js there may be problems with flash. > > On Tuesday, 7 August 2012 20:22:23 UTC-5, Anthony wrote: >> >> I cannot reproduce the problem. Do you have the absolutely latest trunk, >> including the latest web2py.js? > > Good point. But I don't think we can be constrained to make sure that a mixture of both new (updated main.py) and old (legacy web2py.js) parts of the framework continue to work together. A problem would only arise if you're using an Ajax component, in which case, if you upgrade to the new version, you should be expected to upgrade the entire framework, which includes web2py.js. web2py.js is not part of the user's app -- it is part of the framework and should reasonably be expected to be updated with the framework.
Anthony --
