On Thursday, 17 July 2014 04:50:16 UTC-5, lyn2py wrote: > > Hi Massimo, probably a dumb question, but can you explain more why you > would want to move the helper system and form generation to clients side? > Thanks. >
I think it would be nice to have a framework where the server only needs to data (ajax web services) and the forms are generated by JS code based on information provided by those services. > > When do you foresee that Python 3 will takeover the world by storm and > leave Python 2 permanently behind? And when will web3py be ready… hehehe... > Not soon ;-) > I actually like the idea that for one time, web2py will break backward > compatibility to create a better, lighter web2py. Probably won't happen > until web3py, but I'm just dreaming :) > > Love it that DAL is staying no matter what :) > > On Tuesday, June 10, 2014 10:14:03 AM UTC+8, Massimo Di Pierro wrote: >> >> >> I think the future is a lighter web2py with a similar IDE but more >> client-side logic out of the box and more automatic. For example I have >> ported the web2py helper system (DIV, SPAN, etc.) to JS. I would like to >> move form generation also clients-side. I would like move away from the MVC >> and to a mini-MVC patter where an action is responsible for a single >> component (for example validation) and not for an entire page. Wherever we >> are going the DAL is staying! >> >> -- 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.
