Thank you Derek for the suggestion. I was planning in the similar way but wanted to hear the same from experts. :) The application will have only one view finally. That one view will be a extjs application. You are right we cant get web2py form helpers but can you authentication, session management, jsonifying etc. We already have placed extjs library and our custom developed .js in static folders, now planning to integrate all extjs into a single app.
Regards On Saturday, 6 April 2013 01:12:15 UTC+5, Derek wrote: > > I'd suggest all the 'views' be placed in static. Your ExtJS should handle > all the data. Add json services and let the ExtJS consume them. Note that > you won't get form helpers or the security that web2py provides, but you > get the authentication, DAL, automatic jsonifying and caching. > > > On Thursday, April 4, 2013 11:45:28 PM UTC-7, at wrote: >> >> >> HI, >> >> Started working on a project where the team is already working on using >> extjs to develop the views. Each view of web2py application is basically an >> ExtJS application. They've placed extjs library in >> web2py/applications/app/static /extjs and created an extjs_views folder in >> web2py/applications/app/static to place .js files. >> >> I think extjs is not a good choice for developing web2py app views? but >> since they already have invested enough on the project, need an expert >> advice on how should we restructure the whole application in a way that we >> could utilize existing development in extjs. >> >> Thanks & Regards >> >> > -- --- 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.
