Check out what I have done .. www.keithkitz.com
I stripped the main content back to load fairly quick and turned off the Flex application level preloader. I wrote a composite preloader to load all the separate pieces. What I am doing is taking the total number of items to load and using that as a denominator for the total percent needed to load .. so .. if you have say 40 images and you want to preload each one, but you want it to look like it's only one preloader then .. you can kick off the preloader for each image one by one using an array as a queue .. the screen can be updated incrementally to show the percent as each image loads and an accumulator updated for the numerator .. (% image1 + % image2 + % image3 + ... + % image39 + % image40)/40 since the percent for each image preload with vary from 0 to 1 your composite preloader will vary from 0 to 1 .. does this make sense? I can pass you my source if you like .. On Tue, Oct 28, 2008 at 3:50 PM, Baz <[EMAIL PROTECTED]> wrote: > Hi, > > Like most flex apps, mine has a preloader that displays the progress of the > application loading. But unlike most apps, it has dependencies on outside > webservices that need to load as well before anything can happen. I use > remoteobject to load these dependencies and so require that the framework is > loaded before invoking them... right? > I would like the visual experience to be such that only one loading process > occurs - something along the lines of ending the preloading portion at 90% > (rather than 100%), then once the framework is loaded, invoke the > webservices and have the preloader continue from 90% to 100%. > What is the best/cleanest way to go about this? > I don't think I can get a reference to the preloader object once the app has > loaded - can I? So does that mean I should instantiate a new preloader that > starts at 90% to create the illusion that it is continuing? Is this possible > without any visual hiccups, flashes or glitches? If so, what class should > the preloader object be? Right now it extends Sprite but if i try to use > that once the app has loaded it rightly complains that it is not a UI > component. > Lotta stuff in there, thanks for reading it!? > Cheers, > Baz > > > -- Jamie
