I am trying to make an architectural decision on whether to use MVC, or the more traditional Ext.onReady model with Ext Loader.
We have a larg-ish system where available menus vary by user role, and can change at run time (based on admin updates). Also, many of the views have grid fields which can vary based on the definition in a database.
As a result, we cannot define the datastores or controllers at user logon.
When looking into this on ExtJS, I got the impression that either the stores, or the controllers have to be defined in the Ext.application entry point. Is this correct?
Are there any work arounds to this? (eg. nesting one application in another, or defining controllers/stores on a view by view basis).
Are there any dicussion materials or best practice examples on the architectural issues here? I did see Mr. Garcia's article on Ext Loader, but I was not clear how evaluate this against in the light of MVC.
Are there other consideration here, - eg. any plan to retire the traditional approach in favour of MVC?
(I can see how MVC can be great in other applications where offline capability is being considered, or wrapping Sencha applications like Phonegap does).