> Yes I'd be all for replacing the current image loader with this one. Either
> including it as a separate imageloder.js or within dynimage.
I'd vote to separate it from dynimage, because you don't necessarily need
dynimage if you want to use the loader.
dynimage is tied to the current loader, so there are few changes necessary.
i'm going to have a look at it and post an adapted version of it one of the
next days.
> As a suggestion,
> for making the possibility of having a cool progressbar to work along with it,
> allow an option to add the byte-size of the image. This way if you have 20
> small images, and one huge image the progressbar would know the relative
> ratios between images.
i had that idea as well, but then i decided not to implement it because it
adds a bit of complexity to it.. for instance: what should the loader do if
the bytesize hasn't been specified for all images?
however, i'm going to add that feature if it's requested
> The replacement for DynAPI.onLoad will not be a problem, you can just add the
> function to start the image loader with:
>
> DynAPI.document.onLoad(function() {/* your code */});
will every DynDocument have its onLoad-handler instead of the global
DynAPI.onLoad?
--
Michael Buerge
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
