Linked by Thom Holwerda on Tue 20th Dec 2011 22:01 UTC, submitted by RichterKuato
Window Managers Gtk+ has GNOME on the one hand, and Xfce on the other. Qt, on the other hand, only has KDE - there's no lightweight, less encompassing alternative if KDE doesn't float your boat, but you'd still want a Qt desktop. Luckily for you, there's now Razor-qt, a small, lightweight and simple Qt desktop environment.
Thread beginning with comment 500809
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Nice
by Neolander on Wed 21st Dec 2011 14:01 UTC in reply to "RE: Nice"
Neolander
Member since:
2010-03-08

The long-term plans of Nokia (shove accelerated graphics into the hardware requirements, deprecate C++ widgets in favor of CSS+Javascript... err... I mean QML) may be a bit harder for developers to digest, though.

Reply Parent Score: 1

RE[3]: Nice
by Neolander on Wed 21st Dec 2011 17:55 in reply to "RE[2]: Nice"
Neolander Member since:
2010-03-08

How is this inaccurate ?

http://labs.qt.nokia.com/2011/05/09/thoughts-about-qt-5/

A working OpenGL implementation will be required for Qt 5+ software to run. Knowing the fantastic performance of software OpenGL emulation and the new focus on shiny animations and touchscreen gestures, it is likely that a GPU with working drivers will be required for future Qt software to run properly. Fun times for Linux users with recent graphics hardware...

This article also explicitly states that QML + Javascript is the future, and that they expect you to only use C++ for application logic, or even not at all.

I am the first to hope that this madness will cease before it has gone too far, as I like Qt 4 as a framework and it saddens me to see it take that direction.

Edited 2011-12-21 18:04 UTC

Reply Parent Score: 2

RE[4]: Nice
by Not2Sure on Thu 22nd Dec 2011 04:42 in reply to "RE[3]: Nice"
Not2Sure Member since:
2009-12-07

Well the good thing about the new open source governance for qt5 is if enough people agree with you, a consensus should be able to ensure qml-declarative doesn't entirely dominate the direction.

Nokia still pays alot of committer salaries though :|

Reply Parent Score: 2

RE[4]: Nice
by vivainio on Fri 23rd Dec 2011 09:35 in reply to "RE[3]: Nice"
vivainio Member since:
2008-12-26

A working OpenGL implementation will be required for Qt 5+ software to run. Knowing the fantastic performance of software OpenGL emulation and the new focus on shiny animations and touchscreen gestures, it is likely that a GPU with working drivers will be required for future Qt software to run properly.


I have seen Qt5 run on top of Mesa software rendering, and the performance is great.

Reply Parent Score: 2

RE[3]: Nice
by cyrilleberger on Thu 22nd Dec 2011 08:44 in reply to "RE[2]: Nice"
cyrilleberger Member since:
2006-02-01

No they are not deprecated. They are considered complete and mature by Nokia. And while it is true that Nokia is not going to take care of the maintenance, and/or of future development, if there is enough interest, developers can and will contribute. There is still a lot of interest by other companies (especially from the industrial world) to keep funding the development of the C++ widgets for years to come, and also from the KDE and open source side. Also, note that QWidgets and QML share a lot of things in common (like the graphic stack), and one of the main reason of Qt5 is to cleanly split QWidgets, QML and the common stuff.

Reply Parent Score: 4

RE[4]: Nice
by Neolander on Thu 22nd Dec 2011 08:50 in reply to "RE[3]: Nice"
Neolander Member since:
2010-03-08

It seems there is a misunderstanding between us about the meaning of the "deprecate" word.

For me, deprecating a feature is stating "We don't work on this feature anymore, and we expect to remove it at some point in the future, so we declare it legacy. Don't use it in any new software." Which is pretty much what Nokia did in their blog post about Qt 5 :
http://labs.qt.nokia.com/2011/05/09/thoughts-about-qt-5/

I'm specifically thinking about this part :

"We should expect that over time all UIs will be written in QML. JavaScript will become a first class citizen within the Qt community and we should expect that a lot of application logic and even entire applications will be written in JavaScript instead of C++. The expectation is that many application developers will actually start out with QML and JavaScript and only implement functionality in C++ when required."

and this part :

"While the QWidget based classes are extremely important for existing applications, we are, over time, going to move to a model where all UIs are being done in QML. Separating the QWidget based functionality into its own library is therefore a good measure to achieve a clean architecture in Qt 5 in the long term."

Edited 2011-12-22 08:55 UTC

Reply Parent Score: 1