To view parent comment, click here.
To read all comments associated with this story, please click here.
If he writes "KDE", I would guess he means "KDE"... And that makes a lot of sense. I _know_ how much KDE delivers to the office suite builder on top of Qt.
Their current Linux port, the one they couldn't get stable is based on GTK1.
Just for the record, Qt is now also licensed under GPLv3 and comes with a host of licensing exceptions.
Yes, Qt can link to GPLv2, GPLv3, or code under any of the following licenses:
Academic Free License
2.0 or 2.1
Apache Software License
1.0 or 1.1
Apache License
2.0
Apple Public Source License
2.0
Artistic license
From Perl 5.8.0
BSD license
"July 22 1999"
Common Public License
1.0
GNU Library or "Lesser"
General Public License (LGPL)
2.0 or 2.1
Jabber Open Source License
1.0
MIT License
(as attached)
Mozilla Public License (MPL)
1.0 or 1.1
Open Software License
2.0
OpenSSL license (with original
SSLeay license) "2003" ("1998")
PHP License
3.0
Python license (CNRI Python License)
(as attached)
Python Software Foundation License
2.1.1
Q Public License
v1.0
Sleepycat License
"1999"
W3C License
"2001"
X11 License
X11R6.6
Zlib/libpng License
(as attached)
Zope Public License
2.0
I believe the KDE libraries are LGPL, or at least they used to be. I haven't heard anything about the newer ones so I would assume they are the same.
Edited 2008-01-23 15:59 UTC
Developing with KDE4 APIs does not equate to being tied to KDE specifically. Beyond being able to run KDE4 apps pretty well anywhere these days, many of the KDE4 frameworks have no interdependencies making selecting to use one or more of them fairly straightforward and without requiring commitment to the whole kit and kaboodle.





Member since:
2006-09-01
There are two license models for the Qt toolkit. There is a proprietary license for proprietary software with a dollar amount attached to it. Then there is the GPLv2 licensed toolkit for open source software which is free as long as the code is open. Both licenses are cross platform.
, with Qt as the widget toolkit. That would in turn allow them to port Productive to OS X without having to change widget sets. I don't think he meant that Productive was going to be tied to KDE specifically.
Two links to the license matrix and overview.
http://trolltech.com/products/qt/licenses/licensing/matrix
http://trolltech.com/products/qt/licenses/licensing/licensingovervi...
I'm reading this as he meant GoBe Productive would get ported to Linux, and maybe other Unices?