Hi, I prefer the use of a Loader -- in fact, multiple Loaders (if you want to cache loaded SWFs and not have to wait through the initialization stage again.) Combined with RSLs, this should give you an optimum balance between file size, modularity and speed.
hth, Aral -- http://flashant.org 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? ><snip> > -- 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/
