[Interest] QGraphicsView and OpenGL in Qt6

[Philippe]

>>hardware accelerated rendering architecture of Qt Quick is a better
>> architecture than the comparatively monolithic, CPU-bound
>>(...)
>>But if those two statements are true for mobile and embedded, then they
>> are - in principle - also true for the desktop

Though CPU-bound, as you mention, I can tell it is possible to achieve very decent graphic
speeds, for real-time data monitoring, with a classic CPU, even on large
HDPI screens, using the Qt painter API.

This performance could be further much improved if Qt could be built without compile errors using "typedef float qreal"
On Apple Silicon, 32-bit float processing significantly outperforms 64-bit processing (often 2 or 3 times faster).

Philippe


On Mon, 4 Dec 2023 14:55:26 +0000
Volker Hilsheimer via Interest <interest at qt-project.org> wrote:

> > On 30 Nov 2023, at 12:16, Filippo Rusconi via Interest <interest at qt-project.org> wrote:
> >> I know things change but after that little exercise I am not sure anyone
> >> would ever convince me to try QML on the desktop again. Period. If QWidgets
> >> goes away we would probably just move to another language all together
> >> rather than try QML. QML on Phones and tablets? Sure. Go for it. Desktop,
> >> stay away. Far Far away.
> > 
> > +1000
> > 
> > It is some time now that I feel like Qt going the Qml route in a preferred
> > manner with respect to the QWidget route (more revenues, I guess). I hope I am
> > wrong with this feeling. I would be terribly sorry to have to adopt a new
> > library set for widgetry

> 
> 
> 
> First of all: yes, we know that there is still a bit of a way to go before Qt Quick can support everything we want to be able to do on the desktop. What was broken or missing a few years ago might be available, or work better, today.
> 
> But QML vs C++ and Qt Quick vs Qt Widgets is not at all about revenue, it’s about technology.
> 
> QML is a better language for building UIs than C++.
> And the modular, scene-graph based and hardware accelerated rendering architecture of Qt Quick is a better architecture than the comparatively monolithic, CPU-bound approach of Qt Widgets.
> 
> Of course, you might disagree with those statements. But if those two statements are true for mobile and embedded, then they are - in principle - also true for the desktop. Again, we know there’s work to be done to improve desktop-specific use cases.
> 
> So yes, our focus is on making Qt Quick better, and new UI solutions will be designed primarily for Qt Quick. But our focus is also on the technologies that allow mixing the two, so that you don’t have to pick one or the other. You can keep your widget code and add Qt Quick via QQuickWidget to it already today.
> 
> Volker
> 
> 
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> https://lists.qt-project.org/listinfo/interest