For me, having a good supported (backward) path to pick ractive/vue/angular (to big for my need) would be nice... Massimo's has made w3 if I recall, but I rapidly feel lost with ractive.js... I try vue.js and find it easier to pick it up. But there is a lot of boiler plate to implement to levrage vue.js with web2py... You have to step back decide if you are going to properly implement rest in web2py for server side processing and then you have all the form and validation to handle... You can use some vue.js lib for validation, but you have to evaluate them find out if they will be maintain over time before tye you app to them.
My dream would be that we still use web2py to define field constain and that they translate into the front-end while having flexibility to tweak them client site with vue.js that was the point of w3... As Val mention keep the strengh of web2py single dev be able to be as productive as a little team is what would be the most awesome... But with all the possible way to implement things with vue.js or other client side framework, I doubt we could succeed in adoption of this chimera that would make that possible. It would really depend on the burden over extensibility impose by the web2py/vue implementation framework... Richard On Thu, Nov 23, 2017 at 9:05 PM, Carlos A. Armenta Castro < [email protected]> wrote: > Hi Val K, > > I believe the future of Web2Py would be: One back-end and so many flavors > for the Front-End as Flask, Piramyds and Laravel frameworks are doing. My > personal and particular experience using transpilers like rapydscript-ng or > coffescript for a medium size project was very bad (maybe using TypeScript > would be a good idea because of their adoption!). At the beginning with > rapydscript all was easy but mantaint and modify the code was hard for me > (big changes), at the end I re-wrote all my front-end code in pure > Javascript using ES6, Vue and Webpack. Actually ES6 is easy, and the Linter > can prevent us of so many errors. > > https://github.com/eddyekofo94/pyramidVue > https://github.com/gtalarico/flask-vuejs-template > https://github.com/longtranista/django-vue-webpack > https://github.com/dolbex/webpack-laravel > https://github.com/Koroeskohr/rails-vuejs-webpack-boilerplate > > > El jueves, 23 de noviembre de 2017, 13:26:24 (UTC-7), Val K escribió: >> >> I believe that strongest web2py's feature is that it allows to do the >> stuff by one developer, as if it would be done by several qualified one's. >> You are going to make web2py's fans to code in pure JS to develop frontend, >> right? I think it is not the future that's expected. My dream is web2py >> integrated with rapydscript/rapydscript-ng + rapydml + lib of >> vue-components(written on rapydscript) - it would be really fantastic. >> >> On Tuesday, November 14, 2017 at 10:36:52 PM UTC+3, Massimo Di Pierro >> wrote: >>> >>> This is fantastic. Thank you Carlos, >>> please email me personally about you work. I think this is the path to >>> the future of web2py. >>> >>> On Tuesday, 14 November 2017 10:48:03 UTC-6, Carlos A. Armenta Castro >>> wrote: >>>> >>>> I have using Web2Py for too many years for commercial websites and for >>>> Intranets in México, I want to say that Web2Py is an AMAZING Framework!!! >>>> For my new project I need to use an SPA VueJs + Webpack for the >>>> FrontEnd ( http://quasar-framework.org/ ) and a Web2Py as my BackEnd >>>> API Server. >>>> I'm curious about to integrate his two web frameworks using web2py >>>> routes to serve this two apps in the same port but different URL. >>>> >>>> Example: >>>> http://127.0.1.1/welcome/api ---> My Web2py API Controller >>>> http://127.0.1.1/welcome ---> My VueJS APP with webpack ( >>>> http://quasar-framework.org/ ) <-- Pointing to index.html in *dist/ * >>>> and permit to use all the static files deposited in the same path >>>> *dist/** >>>> >>>> *VueJS + Webpack APP Structure* >>>> >>>> ├── *dist/ * *# Compiled APP (Serve this files as the >>>> static SPA)* >>>> │ *└── index.html >>>> │ ├── fonts/ >>>> │ │ └── ... >>>> │ ├── static/ >>>> │ │ └── ... >>>> │ ├── js/ >>>> │ │ └── ...* >>>> ├── config/ >>>> │ ├── index.js # main project config >>>> │ └── ... >>>> ├── src/ >>>> │ ├── main.js # app entry file >>>> │ ├── App.vue # main app component >>>> │ ├── components/ # ui components >>>> │ │ └── ... >>>> │ └── assets/ # module assets (processed by webpack) >>>> │ └── ... >>>> ├── static/ # pure static assets (directly copied) >>>> ├── test/ >>>> ... >>>> >>>> Actually I am doing this work in my NginX Server but I Will be happy if I >>>> can do the same thing easily using pure web2py!!!! >>>> >>>> Why using the same port? Because the CORS issues, this is the best and >>>> easy way to deal with CORS. I know I can use sub-domains in the same port, >>>> I know I can use ALLOW ORIGIN headers in W2P side but that are not options >>>> for me in this case. >>>> >>>> NginX config working: >>>> >>>> location / { >>>> index index.html index.htm; >>>> root /home/www-data/vue/applications/simott; >>>> try_files $uri $uri/ /index.html; >>>> } >>>> >>>> location /api { >>>> uwsgi_pass unix:///tmp/web2py.socket; >>>> include uwsgi_params; >>>> uwsgi_param UWSGI_SCHEME $scheme; >>>> uwsgi_param SERVER_SOFTWARE nginx/$nginx_version; >>>> >>>> } >>>> >>>> Any recommendations? Thanks in advance! >>>> >>>> -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
