I have never used modules so I am not sure if what I am trying to do will work for them or not or maybe there is an easier way to resolve this issue.
I have an app that has several documents. Each document is made of a canvas with an accordian in it. In this accordian I have two vboxes (thus to slides). The first vbox, which is shown on automatically, is a bar graph. The second vbox is a very heavy large custom component that is cpu intensive to create. Here is what I am currently doing, which freezes up my browser. In vbox1 I call this creationComplete="vbox2.createComponentsFromDescriptors()" which means I am creating the children of vbox2 when vbox1's creationComplete event is dispatched. I do it like this so that when the user clicks vbox2 view it, its ready to view and they don't have to wait on it to load. The other way I was doing it was waiting for vbox2 to open and then creating the vbox2's children, which still causes the browser to lock up until it complete, but then they are also looking at a blank background. I tried to use an animation so they would have something to look at, but the animation stops because the browser is locked up do to CPU cycles be eaten up by my heavy components creation being so CPU intensive. I am not sure if moving to a module would solve this issue as I have never used them? Do they load like a flex appliation (progress bar)? And if I go with modules can through events like a regular component so my main app can listen for the events? I am using Mate so if that matters?
