On Fri, Jun 15, 2012 at 6:10 PM, Anthony <abasta...@gmail.com> wrote: > Note, web2py will have the same limitations as any framework in this case.
Right. I just didn't know how much of the Web2py forms "magic" depended-on/required client-side scripting. > Most things should work fine, except of course anything Ajax related > (including Ajax components). Most of what you'll lose can be discerned by > inspecting web2py.js. Javascript is used for the following: Well, as a back-end programmer, what I "discern" is a lot of gobblety gook. I'm using Web2py because I have the backend experience to do the business logic, etc. and want web "front end/gui" interfaces, so I want to "subcontract" all the web stuff that I don't know (or at least not yet) to the expert (Web2py). :-) ...<list elided>... > So, overall, you don't lose anything major, and there are easy alternatives > in most cases. Thanks for that list! As long as things generally work (though it sounds as if the menu might not, I'll have to try that and find out) I'll be fine. > By the way, why is client-side scripting forbidden? I'm looking to deploy a little helper web-app in a corporate environment that's pretty locked down. -=Doug
