[IGSTK-Developers] GUI

[Julien Jomier]

 > We can't have GPL code in IGSTK.  We possibly could have
 > Qt commercial code, but only if any developer who touched
 > that code held a Qt commercial license.  That's a hard thing
 > to regulate, but it is potentially doable.

AFAIK we should be able to develop support for Qt in IGSTK. The new 
Open-source version of Qt requires the following:

- Make the complete source code of your program available to all end users
- Allow all users to re-use, modify and re-distribute the code
- Give up your right to demand compensation for re-use and re-distribution
- Add a notice to your program that it is GPL licensed when it runs

And from the quote:
"If you are unsure of what license you need, then follow this simple 
rule of thumb: If you're Open Source, Qt is Open Source. If you're 
commercial, Qt is commercial."

More info at: http://www.trolltech.com/download/opensource.html

So I think from the toolkit point of view we can redistribute support 
for Qt. Then the users should pay for the commercial license if they 
want to use it in a commercial application, if they are going 
open-source they will be ok.

That said, I agree with David that IGSTK shouldn't be tied to a specific 
GUI toolkit and it will be a good exercise to test it with another GUI.

Julien

David Gobbi wrote:
> Hi Kevin,
> 
> Right now the View classes are still tightly tied to FLTK,
> but there has been definite motion away from absolute
> dependence of IGSTK on FLTK.
> 
> The Qt licensing issue is a biggie... TrollTech is very
> explicit about their commercial licensing conditions.
> Anybody working on Qt code that will eventually become
> commercial, must hold a Qt commercial license before
> they begin working on the code, otherwise the code is
> strictly under the GPL and cannot be converted
> to the Qt commercial license at a later date.
> 
> We can't have GPL code in IGSTK.  We possibly could have
> Qt commercial code, but only if any developer who touched
> that code held a Qt commercial license.  That's a hard thing
> to regulate, but it is potentially doable.
> 
>  - David
> 
> 
> 
> --- Kevin Gary <kgary at asu.edu> wrote:
> 
>> All,
>>
>> We have a dilemma with the validation tool we are writing. For the
>> GUI, it would be better to use Qt, but our understanding of the
>> Qt open source license is that it is GPL and therefore not compatible
>> with IGSTK licensing. Do we misunderstand Qt? I was under the
>> impression IGSTK was considering using it alongside FLTK?
>>
>> Thanks,
>> K2
>>
>>
>> -- 
>> ===
>> Kevin A. Gary, Ph.D.
>> Assistant Professor
>> DCST, ASU East
>> (480)727-1373
>> http://kgary2.east.asu.edu
>> kgary at asu.edu
>>> begin:vcard
>> fn:Kevin Gary
>> n:Gary;Kevin
>> org:Arizona State University Polytechnic;Division of Computing Studies
>> adr:Bldg. 140;;7001 E. Williams Field Road;Mesa;AZ;85212;USA
>> email;internet:kgary at asu.edu
>> title:Assistant Professor
>> tel;work:(480)727-1373
>> tel;fax:(480)727-1248
>> tel;cell:(602)312-7397
>> x-mozilla-html:FALSE
>> url:http://kgary2.east.asu.edu
>> version:2.1
>> end:vcard
>>
>>> _______________________________________________
>> IGSTK-Developers mailing list
>> IGSTK-Developers at public.kitware.com
>> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-developers
>>
> 
> _______________________________________________
> IGSTK-Developers mailing list
> IGSTK-Developers at public.kitware.com
> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-developers
>