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) ?
I'm thinking about creating some kind of TextureResolver interface,
something like
public interface TextureResolver
{
public Texture2D getTexture(URL url);
public void putTexture(URL url, Texture2D tex);
}
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.
As for the interface, I wonder if it should work on Texture objects or
on ImageComponents. Working with textures is easier, but I'm not sure if
application will always know what texture parameters it should set (not
to mention stuff like handling cube maps).
Artur
===========================================================================
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".
