is meteor the answer?
2013/4/18 Magnitus <fbunny2...@hotmail.com> > I'm not even sure I'll go with Angular myself at this point. I'll delve > more deeply into that framework once I feel I have a sufficient grasp of > Ember. > > For the whole server-side dynamically generating client-side, I'm afraid > it's not my vision. > > The direction things are moving toward is to move away from the server > dynamically generating client-side and rather have the client-side generate > itself using data it gets from the server. > > I've done both and I find that having the client-side generate itself is > the cleaner approach in the end (though it probably has a steeper learning > curve, unfortunately). In essence, it makes the "V" part of MVC more > trivial for the server and moves more of that logic on the client-side > where I think it belongs. > > The way I'd see web2py supporting "widgets" is simply to provide some > protocol (currently via ajax) that the client-side expects from the server > to update itself. Maybe also javascript files for different frameworks > (vanilla jQuery, Ember, Angular) if you want some pre-made solutions so > that web2py can be as interoperable on the client side as it is on the > backend (where you can choose from many different servers and databases). > > On Tuesday, 16 April 2013 17:12:48 UTC-4, Niphlod wrote: >> >> >> >> 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 web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- 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.
