yep. when all the logic is pushed client-side, you need just a backend to (eventually) store data, a full-blown MVC server-side framework is not needed anymore.
Anyway, when you start to blob out large chunks of javascript client-side just to do, e.g., an email address validation, you need to choose where the right balance is. On Wednesday, April 3, 2013 7:51:52 PM UTC+2, Derek wrote: > > And that's my whole issue with it, is you'd have two MVC frameworks that > you'd have to work through, or you have static pages and your controller > would just be a link back into the data access layer (DAL). Now, for > Web3py that's maybe all that is needed - create a DAL, authentication, > caching of static content and database calls, and no controllers (you'd > have routes, but that's it). That way your controllers would be javascript > (your javascript framework of choice or just plain javascript) and your > views would be the static html (which would essentialy become templates for > your controllers). However, if that's all Web3py is going to be, then I > could just write my own server using gevent, which would just have > different functions for accessing the database and jsonifying / > de-jsonifying the data. > > On Wednesday, April 3, 2013 10:12:52 AM UTC-7, Andrew W wrote: >> >> Would you use ember with web2py? Why? >> Is having two mvc frameworks at the same time too many? > > -- --- 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.
