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 500949
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Nice
by cyrilleberger on Thu 22nd Dec 2011 08:44 UTC in reply to "RE[2]: Nice"
Member since:

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:

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 :

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