Probably the most significant file to replace is web2py.js, and maybe web2py_ajax.html. There's also the generic views, appadmin.js, and appadmin.html.
Anthony On Sunday, December 23, 2012 9:40:12 PM UTC-5, Tim Richardson wrote: > > > > On Monday, 24 December 2012 01:48:29 UTC+11, Massimo Di Pierro wrote: >> >> Should we just extend this recipe: >> http://web2py.com/books/default/chapter/29/14#Upgrading >> >> or should we also move it? In your opinion, does it belong somewhere else? >> > > I think the location is good. > Most beginner applications will be based on the scaffold app. A discussion > about what happens when you create a new app could link to a discussion > about what files you may need to consider manually upgrading when a new > version of web2py arrives. The best place for details would be release > notes. > > > >> >> On Sunday, 23 December 2012 03:47:43 UTC-6, Tim Richardson wrote: >>> >>> I hope this is not too late. I find it unclear what should be done when >>> a new version of web2py arrives ... What important parts of an application >>> are not upgraded when a new version of web2py arrives, and how to manually >>> upgrade apps to new features of the scafold app. It would be good if this >>> was covered in the book, perhaps. >>> >> --
