Slick Forums

So here's the thing. All the developers have been discussing whether to split the Slick library into multiple packages (slick.jar, slick-util.jar, slick-shader.jar etc.) that aren't necessary to the core (e.g. Tiled, Shaders). Obviously the library is made for you guys, so what are your opinions on it?

I can't find the original thread on it, but it is there somewhere. If someone could link it, that would be useful

_________________
Liam (liamzebedee) Edwards-Playne
Cryptum

for me is okay if explained how to have "old style slick" with new jars

_________________
Blog | Last game Gravity Duck tribute | In progress Gravity Duck tribute

I suppose I wouldn't mind having it either way. All I would have to do is import the jars I need, right? What other advantages would this provide beside limiting the file size for games that don't need the extra stuff?

_________________
Current Testing Machine:
Windows 7 x64, 4GB RAM DDR3, 3.3ghz AMD Athlon II X3 455, AMD Radeon HD 6800 series.

I wouldn't mind. This would actually be pretty nice, since it will cut down on my game size. Then again, it's not much, but if we start adding more things in the future that are not integral to Slick (like Tiled), this sounds like a good idea.

i'm not a fan of splitting them up, because i directly work on the sources
so this would mean that i need to create multiple jar projects or i need
to paste them all in one source bases from all different packages
to work without jars at the end..

slick isn't that big so i would prefer the folders like now, if you don't use an util
you can just drop the folder cause these aren't embedded into the framework as such