We (Philipp and me) using the PreLoader class as a Loader replacement for years now to load asset content (swf's and images). The PreLoader has an integrated loader queue which allows one loading process a time. Also it has some convenience feature like smoothing images when scaling them down.
The PreLoader class is not a visual preloader! You as a developer still has to do the dirty work like listening for Progress and Complete events and react to them. However, you can concentrate on that work without all the (from our point) useless overhead like contentLoaderInfo and URLRequest.
Example implementation:var img:PreLoader = new PreLoader();
function _onImgProgress(event : ProgressEvent)
var perc:Number = event.bytesLoaded / event.bytesTotal;
function _onImgLoaded(event : Event)
}You can find the API documentation here.
What the PreLoader can do for you:Having a loading queue that enabled you to always fill the bandwidth of the user Change the queue during runtime by calling loadNext(), loadAfter() and loadImmediately() Work with the PreLoader just like with the well known Loader only with some tiny but time saving improvements What the PreLoader will not do for you:Group load requests (the PreLoader only has one pipe) Displaying visual loading informations (the PreLoader fires the effect, you decide what to with them) Loading data (PreLoader loads only swf's and images) ContributeWe work a lot with the PreLoader class. It can be called "well tested". However, if you find an issue or miss a feature, please let us know.
These details are provided for information only. No information here is legal advice and should not be used as such.