Loud ramblings of a Software Artisan

Trackbacks

No trackback.

Trackbacks are closed.

Comments

Monday 14 August 2006 20:46, by ralpht :: site :: #

Did you know that I wrote the FLTK support and am currently working on Gtk+ support. I have it running in my own tree, and am using it to write a photo app that uses libgphoto2 (thanks!). Hopefully I will get a release of Mission Photo out soon, and backport my work to mainline ASL so that the next release will support Gtk+ on Linux.

Recent screenshots of my app are here:

www.missioncode.org/blog/

Ralph

Tuesday 15 August 2006 08:43, by Marc :: #

Hi,
I have a newbie question about the license:
I see FLTK is using LGPL "with exceptions that allow for static linking". I thought that LGPL allowed static linking without requiring to release the entire program under LGPL. Am I wrong?

Tuesday 15 August 2006 09:09, by ingo :: #

Yes ;-)

More to the point: GIL is not an imaging library. It is a library of generic accessors and converters for a variety of image types that, in effect, allows you to treat them the same regardless of whether the image has a pixel-interleaved representation (typical RGBA) or banded/planed (every color channel in its own array). Also, some typical conversion routines provided, such as from RGB to gray-value.

Don't get me wrong, thats very usefull on its own, but its not a full-blown imaging library. Its an /image/ library.

Wednesday 13 September 2006 06:30, by Murray Cumming :: site :: #

Marc, no, the LGPL does not allow static linking without requiring the program to be under LGPL. The point of the LGPL is to allow _dynamic_ linking, which the GPL does not allow without requiring the program to be under GPL.

Post a comment

Comments are closed.