I was sincerely impressed with how many things you can do with Angular, but the learning curve is too steep. Then I tried knockout...much better in terms of learning curve, and its methods to map json objects (resultsets) with view-models couples nicely with web2py.....but the templating lacks too much and is a tad bit verbose. Then I tried ractive, and I had a serious headache to figure out how to do "basic tasks" : to be fair, I asked a question on their google-group and got an answer pretty soon: unfortunately the solution was there but the docs weren't updated yet (that's why I had a hard time with it). It seems that the ractive "concept" is closer to my mindset, i.e. it's the tool I'd use to solve "problems" I can't solve with web2py alone, so it "adds" a good value given the effort spent. That being said, there's a whole new concept to adapt to with all of them: your project starts to be python + html and then is python+html+js, with matters like "how do I organize js code within my app", "let's use requirejs" and so on...it's not that easy to adapt if you're coming from python web frameworks.
On Sunday, June 15, 2014 10:34:25 AM UTC+2, Massimo Di Pierro wrote: > > Often Angular comes up on this list. I tried it and I was un-impressed. > Instead today my favorite client-side stack is based on these: > > - jquery.js > - sugar.js > - ractive.js > - semantic-ui (css & js) > > Have you tried sugar, ractive, and semantic-ui? What is your opinion? > > Massimo > > > > > -- 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.
