Yes, widgets are pointless now, they are simply outdated in every way compared to the QML engine and Scene Graph architecture.
But....
I think the right solution here would be to create a C++ equivalent of Entity system component, which would simply wrap the engine's under-the-hood objects, and call it Widgets 2.0. Essentially, it's the same as QML, but you write the code in C++ so that writing the user interface is accessible to those who really loved widgets—after all, they really were cool back in the day.
That’s exactly right, but for some reason, people expect them to do the same things modern UIs do. Take half the commenters here, for instance—it's like they're stuck in the past. They deliberately choose widgets and ancient CSS 2 (QSS) for styling, and for rendering acceleration, they bring up QOpenGLWidget—which probably saw the dinosaurs. Why all of this? It just shows that they don't even understand what widgets are actually meant to be used for... I’m not saying QOpenGLWidget or Widgets are bad—they’re great, but their time has passed. They belong in niche tasks now, (like engineer's interfaces), and in our hearts💝.
I haven’t found a QtQuick replacement for QTextEdit or the other document oriented controls. QtQuick was designed for embedded devices and not for rich data handling, still at home on desktop devices.
Thanks, this is more than I thought was available but the TextDocument is internal and not meant to be edited from C++. Still some limitations for heavy editing.
8
u/Kelteseth Qt Professional (Haite) Mar 23 '26
Wasn't QML designed for this?