On Tuesday, April 16, 2013 1:38:11 PM UTC-7, Magnitus wrote: > > Well, basically, it limited the usefulness of the form facilities and the > tight default integration between authentication and the rendered pages > took some time to bypass
I wrote a while back, about an idea I had for integrating knockout/Angular templating into the HTML helper classes. I see no reason why this idea can-not be extended to refactor the FORM/SQLFOM classes to do the same... The way I approach SAP implementation (in my head...) with web2py, is that you use the web2py views to construct the parts of the pages, as they should be loaded for first-time component-loads and for full-page-refreshes/redirects. This way, if you integrate support for all of web2py's magnificent helper-classes so that they generate SAP-client-side framework templates, you can get the best of both worlds. Granted, for Ember and every other framework using Handlebars, you might have to switch the delimiter-definition of either web2py or handlebars in order to avoid collisions... -- --- 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/groups/opt_out.
