Thank you so much for this post, Frederic. We just starting messing around with 4.0 pretty recently. This was one of our first concerns and we could find very little on the topic. I ignored this post longer than I should of, but only because the implementation was very different from what we needed.
The main difference is that we register external controllers in the launch method of the primary application. The difference for us is that we can redeploy applications all day long without impacting core libraries.
The struggle for us was Ext.Loader. It wouldn't assume the paths we'd hoped until we tried with relative paths.
The attachment is a very simple example of our revised approach. Yoda is the core application, and Sampler uses it.
there has to be full and straight support for multi-viewport and multi-page aap in extjs 4 mvc architecture... else it wont be successful. in real world there are few app with single page and also it had performance issue.
there has to be full and straight support for multi-viewport and multi-page aap in extjs 4 mvc architecture... else it wont be successful. in real world there are few app with single page and also it had performance issue.
I agree and disagree. I agree we need multiple subapplications (it's just figuring the best way to do it and talking people into it). I do disagree that there are few real world single page apps and they have performance issues. I have built lots of large, single page apps and I clean up after things so performance has not been an issue.
Ext JS Senior Software Architect
desktop mvc module
Originally Posted by objectiveanand
Mitchell Simoens @SenchaMitch
Reply With Quote
