On May 15, 2007, at 11:58 AM, Andy wrote: > For small scale projects, I'm sure that the use of XPM would be > fine, but I would like to get used to working as if it were large > scale. XPM just seems too high leveled and uncompressed.
XPM is only usable for images that work a GIFs as well, meaning that you use a lookup table, often limited to 50 or so entries, and a 1- bit transparency layer. PNGs are best if you have a true alpha channel, and JPEGs are best for phot style images. FLTK links to the PNG and JPEG library, and at least fro the Fl_Jpeg_Image class I can say that reading a Jpeg from RAM instead of disk requires only very few lines of code. Storing the compressed jpeg in your executable is a different matter. Which brings me back to my original suggestion: FLUID stores images inside the executable, and even though they are uncompressed (and fast), the do contain all the original channels in full resolution. And even if you don't want to creat you wole UI in FLUID, you can still use this one particular function. ---- http://robowerk.com/ _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
