Artur Biesiadowski wrote:
What is the proposed solution for handling textures in java3d loaders ?
Should loader resolve all of it's textures itself ? Should it cache
them? Or provide hook for user-defined texture loader (but then how it
will work with programs using only Loader interface) ?
The way we've in gone about it in Xj3D is to load all the textures
ourselves. Internally we do our own caching of everything that is
loaded, but we use a static loader to do so. This allows multiple uses
of different instances of the same loader to cache important stuff like
textures.
with default implementation inside loader, if application wants to use
just generic Loader interface.
I have seen TextureLoaderHelper in j3d.org repostory, but it is not an
interface, just util class and it is used only in a3d loader.
You should have a look at the org.j3d.texture package and the
TextureCacheFactory class. We're using this extensively in a number of
projects to do our Texture/ImageComponent object caching.
--
Justin Couch http://www.vlc.com.au/~justin/
Java Architect & Bit Twiddler http://www.yumetech.com/
Author, Java 3D FAQ Maintainer http://www.j3d.org/
-------------------------------------------------------------------
"Humanism is dead. Animals think, feel; so do machines now.
Neither man nor woman is the measure of all things. Every organism
processes data according to its domain, its environment; you, with
all your brains, would be useless in a mouse's universe..."
- Greg Bear, Slant
-------------------------------------------------------------------
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
