"Nobody really uses groups and permissions" Dear Massimo I do use groups and permissions. Groups, use them as roles, and create a copy of permissions to define the permissions as unique. Thus, I grant each user roles and not individual permissions, which allows me to work as in large systems, for which the administration of these cases would be very complex and cumbersome. Sds PS: the apologies for the translator. My English is terrible. > > > It is based on bottle + gevent + gunicorn + rethinkdb + pydal + vue.js + > some code ported from web2py (templates, helpers, validators, > internationalization, scheduler) > > Unlike web2py it uses modules not execfile and this makes it 10x faster > (this part is done) and code it no longer interpreted at every request. > Only on change. > > Routes are declared using decorators like in bottle and flask. > > It will use rethinkdb for storing errors, sessions, and anything user > defined. This allows to scale horizontally. Nothing gets stored on the file > system any more. Ever. Unless you choose to use sqlite for your app. > > No more forms and grids generated server side. Possible and will probably > backport SQLFrom and Gid but will discourage it. The default client will be > in vue.js. The forms and grids will be generated client-side based on > self-documenting APIs. This work must be done. It is not terribly hard just > pedantic. > > It has a redesigned admin. Not necessarily better but leaner. This part is > also done although it may need restyling. > > I am ditching a lot of the web2py auth logic. Nobody really uses groups > and permissions and the way it is done may not be the best way for > everybody. Instead I will default to auth0 integration. > > From a developer prospective the code will look very similar and I will be > able to recycle 90% of the documentation. > > The problems are that web2py grew a bit bloated and typical programming > patterns have shifted from postbacks to single page apps with form > submission via API. Also web2py does not provide enough tools for scaling > since uses filesystem by default. The new version will do less then current > web2py but will remedy those issues and make it easier to make responsive > and scalable apps. > > I am conflicted. I could use help to get this done quicker but I do not > want to post something that is half done people are unhappy with. What I > would like may not be what everybody likes but I am mostly building this in > a way that would work well for myself and share in the hope it is useful to > others. BSD license. > > If you are willing to help before the code is made public feel free to > contact me personally. > > Massimo > > > > > > > On Sunday, 28 May 2017 11:47:49 UTC-5, Oasis Agano wrote: >> >> >> Is the new framework web3py if so when is the official launch? >> On Sunday, May 28, 2017 at 2:32:01 AM UTC+2, Relsi Maron wrote: >>> >>> >>> Hi Andrea, >>> >>> Yes, there will be a future for web2py! >>> >>> Web2py will remain being what it is. :) >>> >>> A new version, with support for Python 3, is about to come. Even though >>> Massimo is developing a new framework, Web2py will continue to exist - with >>> the same purpose for which it was created: to teach development. >>> >>> Cheers. >>> >>> >>> Em sábado, 27 de maio de 2017 04:11:02 UTC-3, Andrea Fae' escreveu: >>>> >>>> Hello guys, >>>> I'd like to know if there will be future of web2py? Any information >>>> about it? >>>> Thanks >>>> >>>
-- 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.
