> Matthias Melcher wrote:
> > On 19.12.2010, at 17:36, Sparkaround wrote:
> >
> >> It is a good idea. But does this break the license of fltk? What should I 
> >> do to fit the license?
> >> Only need make the source code of  MyFl_** availabe to public or the whole 
> >> application based on "MyFl_**". I hope the application can be  linked to 
> >> fltk statically.
> >
> > If you change FLTK itself, you must make the changes public. If you add 
> > your own widgets, even when they are "inside" the library, you do not need 
> > to publish anything. You can link statically, it's a specific addition to 
> > the library because that's what the original developers wanted to do for 
> > their commercial apps.
>
>       I think he's commenting about the idea of making a copy of an existing
>       FLTK widget /code/ in his project's directory so that he can then 
> modify it.


Yes, I am commenting about your copy idea. The class Name in the copy should be 
modified at least to differ from the updated one in the libfltk.a before the 
customized widgets derived from the one in the copy were linked.

>       I think he would then need to make that new code public.
>
>       The way I read the license, I think you'd need to make the new widget 
> code
>       public. ie. post a patch here on the group if it's something you think 
> only
>       a few people could use, or if you think it could be added to FLTK, post 
> an
>       STR as an RFE.
>
>       I did this myself when I added ANSI XTERM sequence support to Fl_Browser
>       so that one could change colors and fonts of text within a single line
>       of an Fl_Browser. This was a weird mod probably not useful to add to 
> FLTK
>       itself, so I posted it on the group as a patch to make it "public".
>       (fltk.development, Subject: "Fl_Browser mod for ANSI" in March 2008)
>
So what I need to do is to post "My_**" together with the patch if have to this 
newsgroup or str. The code based on "My_**" or the patch do not need to be 
published.

Thank you for the detail explanations!



_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to