I like the idea of the Flash Player loading the framework RSL in stealth mode piece by piece when the connection is idle. But we really need to know if the user has the RSL. If they do then we know basic apps are down to 200kb to 400kb. Remember, this *is* comparable to HTML websites with graphics. Once loaded a SWF can be much faster due to only grabbing data. Now you must also consider that most users have broadband and 400kb loads in about 5 seconds. So who is your target audience? They may watch as the preloader zooms across once and you spent way too much time worrying about it. You also realize that those still on dial up are used to slowness on the internet. If a user is on dial up every website they go to takes time to load. The difference is that HTML websites start to give you a preview piece by piece of the site. I thought that possibly a scale 9 "background image" of the complete application can show in the background of the preloader. Give them a preview of what they get if they wait.
some thoughts, - SWF's are cached once they are downloaded (users may have initial load time - show custom message) - RSL Framework (already available but no way to check if user has framework cached) - Flash Player stealth mode downloads the RSL framework in the background during idle network time - RSL Framework broken up into smaller chunks - Super compression of swfs??? (how much are they compressed already?) - Preloader application preview image while loading (sort of like the thumbnail for images or videos in explorer) On 10/21/07, danielvlopes <[EMAIL PROTECTED]> wrote: > > 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] <flexcoders%40yahoogroups.com>, > "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 > > > > >
