Hi, fowleryj I'm using Loader with precompiled SWFs. It feels better a little.
I thought of without using Loader once (following code style) because of performance, but application already use Loader and that is LARGE size. <mx:HBox> <mx:Button label="view1" click="t1.destroyAllChildren();t1.createComponent(0, false);" /> <mx:Button label="view2" click="t1.destroyAllChildren();t1.createComponent(1, false);" /> <mx:Button label="view3" click="t1.destroyAllChildren();t1.createComponent(2, false);" /> </mx:HBox> <mx:ViewStack id="t1" width="100%" height="100%" creationPolicy="none" > ... Best, KAZUYA KOMON ---------------------------------------------------- fowleryj wrote: We are trying to make a decision on how the "shell" of our application should work. Our goal is to load the sub-applications that are a part of our large app dynamically. Basically, should we go with the createChild method or use the mx:Loader tag? We are happy with all of the inner workings of our mxml/viewhelpers/commands/etc, but not with the shell. Would anyone out there mind sharing how you structure your large-scale applications? Are you using a shell with createChild, mx:Loader, or another method? What we have observed so far is this: createChild Good: seems to execute more quickly than mx:Loader Bad: one huge SWF mx:Loader Good: multiple SWFs Bad: seems to execute more slowly than createChild -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
