On Sat, 2013-03-09 at 11:32 +0000, trinity-users-digest-help@lists.pearsoncomputing.net wrote:
<snip>Between the noted performance problems and the fact that the Qt project seems to be completely unable to resolve several bug reports related to incorrect graphics primitive drawing (for example, https://bugreports.qt-project.org/browse/QTBUG-25896), it would appear that the TDE project's decision to stick with Qt3 was the correct decision.
Tim
<snip> Hello, all. I've not been following the list closely for some time because of other responsibilities but the above caught my eye especially as I continually see references to TQT when working in KDevelop on Trinity.
Is TQT a fork of Qt3 as Trinity is a fork of KDE3? If so, is there a licensing issue for Windows TQT applications? Thanks - John
On Sat, 2013-03-09 at 11:32 +0000, trinity-users-digest-help@lists.pearsoncomputing.net wrote:
<snip>Between the noted performance problems and the fact that the Qt project seems to be completely unable to resolve several bug reports related
to
incorrect graphics primitive drawing (for example, https://bugreports.qt-project.org/browse/QTBUG-25896), it would appear that the TDE project's decision to stick with Qt3 was the correct decision.
Tim
<snip> Hello, all. I've not been following the list closely for some time because of other responsibilities but the above caught my eye especially as I continually see references to TQT when working in KDevelop on Trinity.
Is TQT a fork of Qt3 as Trinity is a fork of KDE3? If so, is there a licensing issue for Windows TQT applications? Thanks - John
TQt3 is indeed a fork of Qt3, however it is a fork of the GPLed Qt3 code only. Therefore, TQt3 does not currently support Windows or Mac, however if someone wanted to put in the effort to do so there would be no licensing issues preventing this.
Tim
-
John A. Sullivan III -
Timothy Pearson