Whats holding ~100% D GUI back?

Gregor Mückl gregormueckl at gmx.de
Fri Nov 29 09:05:15 UTC 2019

On Friday, 29 November 2019 at 08:49:33 UTC, Paolo Invernizzi 
> On Friday, 29 November 2019 at 02:42:28 UTC, Gregor Mückl wrote:
>> And rendering the window contents is where things start to 
>> diverge a lot. A game engine is a fundamentally different 
>> beast from a renderer for the kind of graphics a UI draws. The 
>> graphics primitives that GUI code wants to deal map awkwardly 
>> to the GPU rendering pipeline. Sure, there are ways (some of 
>> them quite impressive), but it's a pain. There's no explicit 
>> scene graph.
> As a company that use QT extensively ...
> https://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph.html

Same as with browser engines: Qt Quick gets away with it mostly 
because the UI is declarative. But declarative UIs have their own 
tradeoffs, and in the case if Qt Quick it comes in the form of 
less powerful widgets when compared to Qt Widgets.

More information about the Digitalmars-d mailing list