Supports OpenGL, Software Raster, DirectX, Vulkan(experimental) - all automatically selected for you based on the platform and support.įor example, on Windows, if you want, you can use OpenGL and if the Windows environment doesn't have good drivers and support only OpenGL 1.1, your application will still run since Qt will transparently use Google's Angle and convert on-the-fly calls to OpenGL(ES) into DirectX.Cross-platform and works with different display servers, working on Wayland, X11, Android, Windows, macOS, iOS.

The UI is GPU accelerated(animations.).This is Qt Quick Controls 2.1 from Qt 5.8(soon to be released).

Here it is why I am interested mostly only in QML:

Gleefully embracing UX decisions which defy decades of HCI research (like putting action buttons in the titlebar 'because wasted space' rather than letting natural reading flow place them in the 'end of last line on page' corner)īy process of elimination, even if it were inferior, I'd sooner wrap Qt in a nicer API than use GTK+ 3.x.

Buggy, regression-prone support for hiding GNOME-isms outside GNOME 3 (If I open a GTK+ 3.x app on my desktop, it'll show the traditional and unified 'for putting a menu button in the titlebar' menu bars simultaneously).

Unstable theming APIs driving away developers of themes I like and limiting QGnomePlatform to themes which have been manually ported from GTK+ to Qt (unlike QGtkStyle).

GTK+ 2.x is a legacy solution on life support, so that's not an option. Qt, GTK+ 2.x, and GTK+ 3.x are the only mainstream toolkits for a Linux desktop which people aim to unify theming across, so it has to be one of those. It's also that I insist that my applications have a consistent look and feel. Although, Qt now can get a little bit smaller too. The nice thing with Rust though is that the dependencies are A Lot smaller. The rest is available in the Rust ecosystem(maybe not all, although I cannot think of the top of my head what is missing except for the GUI stuff, Qt Service Framework and the State Machine Framework). To be sincere though, the only thing I am interested from Qt is QML. One way to make it easier would be to 'start' the Rust code from within Qt because of the Event Loop(QCoreApplication and in general every QThread has its own Event Loop, without it you can't have signal/slots). Moc is not that awful(and for signal/slots you basically need to implement moc for Rust), you could get some inspiration from it or from Verdigris(same developer). I will look in the weekend on all the mentioned implementations and maybe give some feedback. My daily job is actually working with Qt(components like a CacheManager) and on Qt(the code itself - we deliver it to other projects) - so I might be able to help here.

Qt slot machine program