you can now find an example and a documentation here: http://n.ethz.ch/student/mibuerge/dynapi-2.54/imgobj_demo/example1.htm
it's very rough and the DynAPI-Version is outdated, but it should show the basics. it also shows that integration with dynimage is easy. after all, my code doesn't replace DynImage itself, it just replaces the loader. i never noticed the NS4.03-bug (i just don't have that version), but the workaround you mentioned would be easy to add. another idea would be to set a timeout to give it at least a chance to preload the images correctly. i'm not sure if i can offer a solution for the problems you currently have with DynImage, but if you specify the size of the image yourself and don't rely on the values detected by the browser, you should be on the save side. not sure if i got this right... as for the DynAPI.onLoad beeing deprecated in a future version of DynAPI maybe i didn't get the point, but if you wan't to do image-preloading there has to be some kind of handler that gets called after stuff has been loaded. i have to go now, my life is waiting... -- Michael Buerge ps: damn reply-address! and richard: sorry again! > From: "Richard Bennett" <[EMAIL PROTECTED]> > Date: Mon, 12 Nov 2001 11:09:14 +0100 > To: Michael Bürge <[EMAIL PROTECTED]>, > <[EMAIL PROTECTED]> > Subject: Re: [Dynapi-Dev] image-loader > > Hi, > As usual you have some very nice code in there. > > A few points: > A few examples would be welcome. > Support for .PNGs would be desirable. > We have a choice, release this as an optional component, in an add-on pack > (with all the animation routines etc), or, replace Dynimage. > If we want to replace dynimage, I would have been keen to replace it with > something more light-weight... > As Dan is more active in this project again, I would like to hear his view > on replacing dynImage with this code. > The main problem we have with DynImage at the moment is, that some widgets > resize themselves to the size of an image, this fails in Mozilla/NS6/IE5.5 > (when run off a server). Would your code offer a solution for this? maybe > add an eventlistener for the onload event, and get the size then? > What I like about this code is that it uses the onload and onerror events, > instead of setting up a loop listening for the complete state. There is > however a bug in NS4.03 , which doesn't return the onload event reliably. I > personally think we should strive to support NS4 from the first versions > where possible, and an easy workaround is to let NS4.03 slip through the > preloading, more info here: > http://www.htmlguru.com/content/tutorials/curious_eye/index.html > In Dan's new proposed code, the DynAPI.onload event is depreceated, so some > rethinking would be needed there. > > > Cheers, > Richard.
imgobj_demo.zip
Description: Zip archive
