The main goal is to make it as close as possible to web2py but faster, allow more flexibility and move more logic client-size. It will be smaller than web2py.
admin will look different but have similar functionality. the request/response objects will be the bottlepy ones. dal & templates are the same as in web2py, therefore most of the logic will be similar. routing will be done with decorators like bottlepy and flask. scaffolding app will promote single page apps with vue.js and auth0 instead of native template system. nothing (except apps themselves) will be store on filesystem because we found that to be a scalability bottleneck. thinking about integrating websockets ot http push notification or integration... the folder structure will be similar to web2py's (applications, applications/databases, etc) but it will use import not execfile and will give more flexibility to organize individual apps internally. apps will be able to import each other modules and models. Massimo On Saturday, 15 April 2017 20:30:52 UTC-5, pbreit wrote: > > I love web2py but am excited to hear about your next framework. When do > you think we might see a functional/preview? will it be recognizable to > web2py users are a big departure? What are you thinking for the front-end, > template/views like web2py or something more JavaScript like React/Vue? > -- 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.
