On Tuesday, April 16, 2013 10:38:11 PM UTC+2, 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 and then there was stripping the layout.html file > to it's bare essentials. > > Overall, I've always been much happier to use web2py for it's server-side > features and let it be a flexible interface with which 100% custom-made > client-side code could interact. > > yeah. the real problem is that no-one working on angularjs is making public its own widgets. All that it takes is overloading SQLFORM.widgets and given that we ship web2py with a formstyle parameter that can be a callable from some time, all that is needed is something that generates angular templates out of models (and someone that is willing to do it). Once stable, that formstyle can be included in standard web2py and the "newwidgets.py" module shipped in gluon/contrib. then SQLFORM(thetable, formstyle='angularjs') will be all what's needed
Right now I don't have any interest in angularjs so I call myself out of the competition, but feel free to pack a starter app and I'll be more than glad to review the code. -- --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
