Linked by Thom Holwerda on Tue 1st Nov 2011 21:31 UTC, submitted by Z_God
Permalink for comment 495212
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2011-11-01
Hey I am a developer for Trinity
We Actually maintain Qt3 as of this release. This means we've been adding patches, and pulling in the many dozen patches from distributions that have piled up over the years.
As for Qt4, it's in beta. We actually have a abstraction layer for Qt called TQt. this will allow us to use Qt4, Qt5, Qt3, whatever, concurently and effectively. Reduces the porting effort majorly.
Funnily enough we've had A lot of QA issues with Qt4, some stuff just plain doesn't work, or has been really dumbed down from Qt3. Qt3 is much faster and works well, but we are definitely in the process of being able to use Qt4 optionally.
We have those applications in our SVN tree and repositories. Basically we maintain them now. This means we've been patching them to work with our latest libraries (which have changed quite a bit, broken the ABI compatibility). Typically this process is pretty simple, this release we have added 3 "new" applications to repository. We are looking to add more as well. Right now we have
probably 50+ applications, from Digikam to Amarok and the whole KDevelop Suite.
Edited 2011-11-01 23:24 UTC