I had made a library, which would load PNG, and JPEG images into a
directbuffer.
I am now converting it to a ggi extension, and I have a few implementation
questions:
1) I am currently using a proprietary struc (ggiImg...) which contains
width, height, pixelformat, data_layout, and data... would it be better
if I used a ggi_visual instead, and just used the in_memory target if I
want to do off-screen work, that way they could use the image transforms in
a doublebuffer, or offscreen, etc w/o be making a bunch of special cases in
my functions...
2) I am making a lot of image tranform functions, should they be in ggiImg, or
another extension, as if I use a ggi_visual they would work on any pixel
buffer...
...
3) I have already made a working(but messy still) dynamically loadable guile
module for libggi, would anyone be interested in cleaning it up, and
maintaining it for a while?
:) My next extension will be ggiGlyph, a unicode font rasterizer...
-Kor Grey <[EMAIL PROTECTED]>
