in addition to what mdpierro said, I'd argue that the best solution is overriding, which can be done with the recent web2py.js versions. If a new version comes out, you'd need to review the changed functionality and update the custom overrides accordingly. We do this already https://github.com/web2py/web2py/blob/master/applications/welcome/static/js/web2py-bootstrap3.js
On Thursday, August 6, 2015 at 8:13:58 AM UTC+2, Massimo Di Pierro wrote: > > Why do you need to change web2py.js? I have nothing against. I just would > like to understand if there is something we can do to make it more general. > > On Thursday, 6 August 2015 00:41:12 UTC-5, Joe Barnhart wrote: >> >> It seems more and more clear I'm going to be making changes to the >> included web2py.js file. I'm worried about keeping current when new >> versions of web2py come out if I've mucked a lot with this javascript file. >> >> So what does everyone else do? How do we customize the platform and >> still keep current with its evolution? Is there an accepted "best >> practice" in this area? >> >> -- Joe >> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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/d/optout.
