MCO wrote:
>> imacarthur wrote:
>>> On 3 Apr 2009, at 10:42, MCO wrote:
>>>
>>>> Hello FLTK programmers,
>>>>
>>>> I recently wrote some FLTK-related blog posts I'll share here.
>>>>
>>>> The first one shows how to use the light version of the Anti-Grain
>>>> library from fltk ( less featured than full AGG, but small code) :
>>>> http://dtedm.blogspot.com/2009/03/fltk-agg-lite.html
>>>>
>>>> The second one shows how the tinyscheme interpreter can be used from
>>>> Fltk, in two parts ( I might add some further examples) :
>>>>
>>>> http://dtedm.blogspot.com/2009/03/fltk-tinyscheme-1.html
>>>> http://dtedm.blogspot.com/2009/03/fltk-tinyscheme-2.html
>>>>
>>>> Of course, this should be considered 'proof of concept' code but, hey,
>>>> I thought it might prove useful to some of you guys.
>>> This looks really nice. We already (sort of) have Cairo support, but I
>>> was always keen on AGG too, so this is a Good Thing.
>> IIRC, the full AGG license isn't suitable for FLTK (GPL or some other
>> licence not compatible with commercial developers); not sure what the
>> "lite" version uses, though...
>>
>> --
>> ______________________________________________________________________
>> Michael Sweet, Easy Software Products mike at easysw dot com
>
> Hi Michael,
>
> here's what's included in the .C and .H files :
>
> // Anti-Grain Geometry - Version 2.1 Lite
> // Copyright (C) 2002-2003 Maxim Shemanarev (McSeem)
> //
> // Permission to copy, use, modify, sell and distribute this software
> // is granted provided this copyright notice appears in all copies.
> // This software is provided "as is" without express or implied
> // warranty, and with no claim as to its suitability for any purpose.
> //
> // The author gratefully acknowleges the support of David Turner,
> // Robert Wilhelm, and Werner Lemberg - the authors of the FreeType
> // libray - in producing this work. See http://www.freetype.org for details.
>
> I'll admit I'm no specialist in these matters but it looks fine doesn't it ?
Still, I'd suggest getting the author's permission before "changing"
their license, even if it seems like there's no net effect.
Taking code from the outside and including it with FLTK implies
the merging software becomes under LGPL control, effectively
changing the author's previous license.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk