On 5/20/06, Peter Bex <[EMAIL PROTECTED]> wrote:
Looks like it doesn't depend on X. I'll see if I can find the time to make the imlib2 egg to compile without X. (and implement a GC hook for destroying imlib2 data while I'm at it)
Sounds great.
I meant creating a so-called "loader" for imlib2, the C library. Loaders are like "plugins". All file formats imlib2 supports are implemented through a loader. Most loaders are quite simple interfaces to existing image libraries (like libjpeg, libpng, libtiff etc) Most of these are just a few hundred lines. Check out src/modules/loaders in the imlib2 source distribution. Creating a new loader means all imlib2 programs automatically (without ANY additional code) benefit from it, including Chicken programs which utilize the imlib2 egg. The egg doesn't even need to be updated! I hope you agree this is the superior way to do this. If you create a libexif egg, it means you have to conditionally use either libexif calls for exif images or imlib2 calls for any other image format in your program.
Understood. Loaders definitely sound a better way to go about. I definitely need to relearn my C and all. First, I need to learn about the dev environment and all. Neither Turbo C and the embedded stuff I did counts. One of the reason I am sticking with chicken instead of something like SISC is so that I will hopefully do some C too. For me choosing SISC and Java is really very easy, and according to Buddist teaching (so I am told) the right path is always the one that is difficult ;) Cheers, Ashish _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
