Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
slint
Slint is a declarative GUI toolkit to build native user interfaces for Rust, C++, or JavaScript apps.
-
qskinny
A lightweight framework on top of the Qt scene graph and only few classes from Qt/Quick. It is usable from C++ and/or QML.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Most big media author apps are written with Qt. Da Vinci Resolve is a Qt app, so are Cubase, Maya, Substance stuff... Natron... Kdenlive... Qt is part of the standard toolkit for VFX apps if I'm not mistaken also. I'm developing a DAW/media art-ish app with it: https://ossia.io and am super happy with it.
Yes but the better way is through Qt styles. I used https://github.com/randrew/phantomstyle + some custom changes + a custom palette : https://github.com/ossia/score/blob/233932c99139d11b4d90fc497bc14005985cb8aa/src/app/Application.cpp#L189
I've detailed some of the rationale here: https://github.com/vgc/vgc/issues/200
I'll just do some self-promotion and drop a link to an alternative new GUI toolkit: Slint https://slint-ui.com/
Do you think that an approach like QSkinny would work for you? I've not used it myself in practice (just running the examples, and looking at the code), but the idea of it is that it uses Qt Quick as a backend (so I guess in Qt 6 it would use OpenGL/Vulkan/Metal/etc as needed without you having to do the abstraction), and IIRC it uses some of the private APIs that Qt Quick Controls use as well for the C++ side. QSkinny doesn't require to use QML though (should be optional, but I think C++ is preferred/more tested). It has been said also that during the Qt 6 timeline, there might be a C++ public API for Qt Quick Controls.