As you may have seen, LWJGL 0.93 comes with the new DevIL (also known as OpenIL) binding. For those who don’t know about it, it’s a very useful toolkit to load textures with OpenGL, very easy to use and so damn fast…
At the moment, the binding is in an early build, so it doesn’t have all things you can find into the original DevIL, but it will support JPEG, GIF, TGA, DDS and others format like that…
Do you plan to use this lib in the future ? It would remove the AWT/Swing dependencies for texture loading and could improve the performances…
Chman
http://openil.sourceforge.net/
Looks cool…
Will their choose of license (LGPL) complicate things? I’m not very good at juridical stuff…
LGPL is a good license because you can sell your game with the thing without paying royalties… But I don’t know if you must put your source code in the package…
Chman
There’s a couple things to look at before making use of it. First, yes, the license… which confuses me how LWJGL mixed it in as they are BSD like us. Mixing licenses is never a good thing. Second, JOGL support is on the cards soon, and the current image loading (while needed work on speed, etc) would work in both LWJGL and JOGL. It’s definately something worth looking into though.
Good, then that’s not a worry.
We could use DevIL for lwjgl and swing for jogl. This would solve the problem on mac.
"Badmi" wrote:
We could use DevIL for lwjgl and swing for jogl. This would solve the problem on mac.
Would be good ! And maybe Jogl developpers will work on a "Joil" binding in the future...
Chman
Any license issues with DevIL also applies to OpenAL. Both are based on LGPL. As far as we are aware there are no issues whatsoever in creating a binding like we have done, since we only link to the code. I have confirmed this with the author of DevIL and he agrees.
Should someone decide to modify the actual OpenAL or DevIL code, then that will ofcourse bring about some issues…
The license issue is something we are keenly aware of!
Thanks, Matzon. Good to know. Didn’t want to bring any undo hardship.
Anyways, don’t expect the TextureManager to be converted anytime soon, but we will definately look into switching. Right now, however, it’s a working system and there are more pressing matters.