The new version of web2py_ajax.html/web2py_ajax.js should work the same as the old web2py_ajax.html, so you shouldn't need to update if you don't want to. Most of the original file was separated into a .js file in static (a) so the content can be cached by browsers instead of being sent on every request and (b) to make the JS more portable and easier to use outside the context of web2py_ajax.html (i.e., without requiring web2py template processing to generate). In general, when you upgrade to a new web2py version, you shouldn't need to update your applications, though you may want to in order to take advantage of some new features (or bug/security fixes). Anthony
On Sunday, June 26, 2011 4:36:37 PM UTC-4, sebastian wrote: > Hi All, > > just wondering how strongly coupled are the web2py LOAD with the ajax > componetnts present in the applications... (web2py_ajax.html and > web2py_ajax.js for example) > > I mean, would an old application that works fine with an old web2py, still > work on a newer web2py version which has changed also LOAD, > web2py_ajax.html and web2py_ajax.js ? > > Just wondering how difficult would maintaining one (many) application(s) > be as everytime that I've update I need to update web2py and update all the > applications static files related to web2py... > > Thanks > -- > Sebastian E. Ovide > > > > >
