An Image widget does make sense, but there are some problems with DynImage. There are some bugs with it, and some the preloading code isn't really needed (keeping a list of image src's etc).
DynImage is a better option that writing the <img> string in a DynLayer because you have extra Image specific functionality, like resizing that image, and easy image swapping (with auto resizing). It's just the idea of adding extra functionality that is often needed - that's the point of an API isn't it? Dan Steinman On Wed, Oct 17, 2001 at 05:51:58PM +0200, Jordi Ministral wrote: > Someone please convince me it is worth using. Honestly I think that's > forcing things too much: an object that encapsulates the already > existing Image object... > > > _______________________________________________ > Dynapi-Dev mailing list > [EMAIL PROTECTED] > http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/ _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
