I think the framework caching is right way to make swf files smaller. But even i know not all apps for flash player not use flex framework i think this 500kb framework file must be loaded not when user try use some flex app, but in stealth like flash player update (i don't know it is possible) but i think this is one way to make swfs file smaller and user don't worry of 500kb dowload.
Or maybe break framework in smaller files, and this files loaded and cached in persistent cache on demmand. Or maybe let developers specify what they using and mxmlc compile a new framework file (copy of original and still assigned by adobe for persistent cache) and this new part framework file append of other parts user dowloaded. I don't know if this options are possible, only ideas... One think i know is i will be extremely happy if adobe can make swf files small. --- In [email protected], "dave_defusion" <[EMAIL PROTECTED]> wrote: > > > It there was a way that I could load the modules in the background while > > the user is doing other things would be great, then it would be there > > right when I need it. > > A quick Google search would have shown you that this is possible with > modules, by doing ModuleManager.getModule("MyModule.swf").load();, > this will load the module but not display it, so when it's time for > you to display it it's already been loaded. > > However the only time you should really do that is if you're sure the > user is going to use that module while using your app. One of the most > common cases for using modules seems to be when you have sections of > your app (e.g. a preferences section) which the user isn't always > going to require - so you only load that when they want it. > > -D >
