Large Application Architecture Question...
In a new application redesign we are working on, we are looking to translate a very large application (which has approximate 10 first level tabs, and each parent tab may have 10 children tabs). Again, each page is portal like, and may have grids, trees, html, graphs. In the first application, I know that the source is loaded in, then becomes part of the page source. I am a bit afraid of loading each tab into the page source, since each page may be heavy, and the page source and memory may become very high.
Any ideas/discussion if others have done something similar would be greatly appreciated.
Hope all are well.
Sencha Premium Member
One method you could try is to build xtypes of all your components. Then you could dynamically load the scripts after checking if their xtype exists or not before you invoke the component.
Maybe also check out $JIT and JScout extensions
I haven't heard of the $JIT and JScout extensions...I will check them out, since I definitely don't know what they are or how they are used.
The question I had on loading the xtypes and then dynamically loading the scripts is that eventually, I would think that I would run into the same situation as just lazy loading everything...as the user clicks through the application, everything would be loaded into the source.
Do others have experience with using an iFrame in the center region, which would change when the user clicks a tab? Could this somehow reuse the ext-all and other application libraries loaded into the "parent" frame?
Just wanted to see if anyone else had any ideas on large scale applications?
Thanks again for any help/discussion.