And it is absurd to call KDE a "tech demo for Qt". 90% of the stuff you can with the KDE you cannot do with Qt because KDE adds a ton of additional functionality. That is why it is so rare to see Qt-only Linux apps, KDE adds so much additional functionality there is pretty much no point.
"Hey, this is KDE. Look at what you can do with Qt"
"Cool, so I just download Qt and I can make my application do all that?"
"Well...no..you need to download tens of megabytes of additional KDE libraries to do most of those things...but the low-level stuff runs on Qt!"
"So why exactly should I use Qt instead of KDE?"
Yeah, great tech demo there...
You apparently don't know the difference between "deprecated" and "feature complete". QWidgets are considered feature complete, not deprecated. That means they will be in Qt 6. The may be marked as deprecated in Qt 6 and removed in Qt 7, but that is probably 15 years away.
1) File bug reports
2) Test it on a system other than Debian/Ubuntu based before you really make a judgement.
Why #2? Ubuntu and Debian add patches, pull from git, backport changes, they do a lot of crap that can screw it up. Its one of the reasons I moved to Arch, I got tired of Ubuntu messing with Upstream. At least with Arch I know its from an actual release branch (not git-master) and they probably didnt add patches in. My recommendations are Arch (obviously) or openSuse, if either of those distros still have the bugs you're facing (you could prob test openSuse from the latest release candidate live image) then report them. If not, chalk it up to being library version incompatibilities since you're mixing PPA's / patches from non-upstream / random ubuntu crap.
I have had literally NONE of the problems you're describing, though I dont use the comic strip (do use the weather though, no problems) so its got to be something specific to your combination of software (/software versions)
Qt5 Widgets aren't feature complete if e.g. hardware acceleration isn't supported unlike QML. Widgets are deprecated if Digia has decided Widgets won't support hardware acceleration.Quote:
Plasma Workspaces have been refined considerably. Work continues on updating widgets with new ones built with Qt Quick. This effort brings improvements in consistency, layout behavior, stability, ease of use and performance. It is also now easier to build widgets, entirely new Plasma Workspace layouts and other custom enhancements. A new QML-based screen locker makes Workspaces more secure.
List of features supported by QML but unsupported by Widgets will grow which will cause devs to rewrite apps using QML.
When all big apps will be rewritten, Digia will drop Widgets to save manpower needed for maintenance.
On the other hand QML has absolutely no benefit whatsoever for most desktop apps. Unless it is something that needs a lot of very fluid animations, like widgets or games, QML provides no benefit, in fact in some ways it makes it harder.
Besides plasma, look at the QML applications being created right now. They are pretty much all completely separate applications from the desktop versions, only sharing underlying libraries and logic. Even in these situations, the situations where you would most expect them to want to use QML on the desktop, the developers have no plans whatsoever to port the desktop applications to QML.
So yes, when all the major apps are no longer using qwidget them may deprecate it. But that looks to be a very, very long way off.
QML has been around for over 3 years now, nearly half the lifespan of Qt4, and there is no move whatsoever towards porting any desktop applications to QML besides workspaces and games.
Don't get me wrong, we probably will start seeing QML used to a limited extent in situations where its animations are needed. But all indications right now are that those will be the exception rather than the rule.
Qwidget was the original set and therefore a very large part of KDE is using that. QML was later gaining ground and has effectively replaced QWidget as the default class. Rewriting anything Qwidget into QML is a non-trivial task.
I'm not sure if all is all that bad in the long run, if only maintenance of QWidget can be kept. From the arstechnica link:
FWIW, also former Gnome-lover Canonical is in the same boat since two years, once they voluntarily jumped onto the Qt boat (http://qt-project.org/forums/viewthread/3214):Quote:
QML is designed to take advantage of Qt's powerful model/view/controller (MVC) framework, meaning that existing Qt applications designed around Qt's MVC classes will be easy to refit with a QML user interface. This opens up a path for bringing existing Qt desktop applications to mobile devices. Developers merely have to add a few roles to their model and then expose it to a QML view, where a touchscreen-friendly interface can be created with a little bit of declarative scripting.
That should mean something for the long run.Quote:
The “Unity 2D” desktop is to provide a Unity environment without the need for OpenGL or any accelerated graphics drivers, but is built using Qt and QML.
From that perspective alone, the QWidget class is deprecated, not KDE dying.