May we ? As I suggested with collision detection code and with non-blender-supported MD2 loader we could just put it in a separate jars downloadable in an “Archive” section on Xith web site… So we could rename TextureLoader2 to TextureLoader and make sure users who still were at TextureLoader v1 switched.
I already switched various loaders (OBJ, 3DS, MD2) to TextureLoader2 and also some demos.
As long as previous builds are still available then I say drop it. There seems to be a worry with Xith that changing the API make break some phantom users - however, since Xith isn’t at 1.0.0 yet API changes are kinda expected. As long the migration path from version to version is fully documented seems like the thing to do.
The last thing you want is dregs of old API hanging around when you don’t need it.
Kev
I use it, but won’t mind switching to TL2 (i’ve already started working on it)
Lilian
OK.
(But, heh, weren’t you complaining about the painful JSR-231 witch ? ;D ;D ;D okay was my fault. apologies)