- We already use PNG/TGA/etc formats to serialize image data.
- What about consistency with all other asset types? Sounds, sprite sheets, etc?
- What's the purpose? How will the code changes benefit users? Is it worth the time and effort? Keep in mind that (generally speaking) adding new things introduces new bugs and problems.
These kind of things may be better envisioned as an extension, rather than changing the Slick lib. It's very easy to set up a github project, and we could even link to it in the wiki.
For example, I have a "PixelData" utility that I'm not sure is really needed for Slick, but I figured it's important enough to mention it in the wiki:http://slick.cokeandcode.com/wiki/doku. ... ta_utility