> One library that does not use LibGGI and does not know about visuals.
> It should dynamicly load readers/writers for different image formats,
> and read images into/write imaghes from it's own simple structure
> (basicly just width, height, format and a pointer to the data).
Please not. Optionally yes, but don't load images into memory without need.
A callback oriented approach would be much better. I've been bitten by that
"oh, just put it in memory" concept too many times ...
Adding a few simple "example-callbacks" that render into such a structure or
a LibGGI visual can give the same ease of use if desired, but without
straining my swap, if I don't want that.
> It should also be able to convert images between different formats.
That could be done by chaining a load and a save call appropriately.
> The second library should be a simple glue-layer between the first
> library an LibGGI. The reason to make two libraries that a generic
> image loader/writer that is _not_ tied to any graphics/window system
> is badly needed, and the first library will be just that.
Yep.
CU, Andy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
