Hi,
I'm just wondering whether someone has looked at/considered using Qt5 with Trinity. There was an article recently from the LXQt people which was quite positive about its memory usage: https://blog.lxde.org/?p=1364
I'm aware that there have been concerns that Qt4 (so maybe Qt5 too?) has significant dependencies on having a fast GPU to get performance while Qt3/TQt will work much better when a GPU is not available.
Best regards, Julius
On 2016/10/10 06:45 AM, Julius Schwartzenberg wrote:
Hi,
I'm just wondering whether someone has looked at/considered using Qt5 with Trinity. There was an article recently from the LXQt people which was quite positive about its memory usage: https://blog.lxde.org/?p=1364
I'm aware that there have been concerns that Qt4 (so maybe Qt5 too?) has significant dependencies on having a fast GPU to get performance while Qt3/TQt will work much better when a GPU is not available.
Best regards, Julius
Extremely unlikely unless an army of volunteering developers suddenly decided to join TDE :-) It would probably take ages with the current developer workforce we have available, which is why the original plan to move to qt4 was put aside some time ago. Cheers Michele
Op 11-10-16 om 10:47 schreef Michele Calgaro:
On 2016/10/10 06:45 AM, Julius Schwartzenberg wrote:
Hi,
I'm just wondering whether someone has looked at/considered using Qt5 with Trinity. There was an article recently from the LXQt people which was quite positive about its memory usage: https://blog.lxde.org/?p=1364
I'm aware that there have been concerns that Qt4 (so maybe Qt5 too?) has significant dependencies on having a fast GPU to get performance while Qt3/TQt will work much better when a GPU is not available.
Best regards, Julius
Extremely unlikely unless an army of volunteering developers suddenly decided to join TDE :-) It would probably take ages with the current developer workforce we have available, which is why the original plan to move to qt4 was put aside some time ago. Cheers Michele
I remember it was mainly about performance. I actually have a repo on GitHub which has a version of Kicker that runs on Qt4/KDE4. I also remember Tim had Trinity mostly working against Qt4 but he saw a lot of performance issues.
Having a Trinity-like DE on Qt5 could probably mostly be achieved by porting just Kicker and KDesktop to Qt5/KDE5 and having a session with those instead of Plasma. That wouldn't make sense if performance would suffer significantly though.
There was also the recent announcement about Qt Lite. It's supposed to run on systems with as little as 16 MB of memory and doesn't require OpenGL: http://blog.qt.io/blog/2016/08/18/introducing-the-qt-lite-project-qt-for-any...
Maybe these developments are out of scope for the Trinity project already, but it would be interesting to hear if anybody had compared them with Qt3/TQt.
Best regards, Julius
On 2016/10/12 11:10 PM, Julius Schwartzenberg wrote:
Op 11-10-16 om 10:47 schreef Michele Calgaro:
On 2016/10/10 06:45 AM, Julius Schwartzenberg wrote:
Hi,
I'm just wondering whether someone has looked at/considered using Qt5 with Trinity. There was an article recently from the LXQt people which was quite positive about its memory usage: https://blog.lxde.org/?p=1364
I'm aware that there have been concerns that Qt4 (so maybe Qt5 too?) has significant dependencies on having a fast GPU to get performance while Qt3/TQt will work much better when a GPU is not available.
Best regards, Julius
Extremely unlikely unless an army of volunteering developers suddenly decided to join TDE :-) It would probably take ages with the current developer workforce we have available, which is why the original plan to move to qt4 was put aside some time ago. Cheers Michele
I remember it was mainly about performance. I actually have a repo on GitHub which has a version of Kicker that runs on Qt4/KDE4. I also remember Tim had Trinity mostly working against Qt4 but he saw a lot of performance issues.
Having a Trinity-like DE on Qt5 could probably mostly be achieved by porting just Kicker and KDesktop to Qt5/KDE5 and having a session with those instead of Plasma. That wouldn't make sense if performance would suffer significantly though.
There was also the recent announcement about Qt Lite. It's supposed to run on systems with as little as 16 MB of memory and doesn't require OpenGL: http://blog.qt.io/blog/2016/08/18/introducing-the-qt-lite-project-qt-for-any...
Maybe these developments are out of scope for the Trinity project already, but it would be interesting to hear if anybody had compared them with Qt3/TQt.
Best regards, Julius
Thanks Julius, I think performance was one side of it, but the other one was manpower as well (I wasn't around at that time, so I may be wrong...). Now it would surely be manpower, given we are just 4-5 developers in total, often not all present for some time due to personal work/life commitments. So I think that for the time being, TDE will remain on TQt3, unless Tim comes around and has other ideas about it (given that he is the project coordinator after all).
Cheers Michele
-
Julius Schwartzenberg -
Michele Calgaro