Took a look at the available options. This appears to be your best bet. Otherwise there are a few others, although less advanced and/or less maintained
this post was submitted on 22 May 2025
20 points (100.0% liked)
KDE
6587 readers
182 users here now
KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
Plasma 6 Bugs
If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
founded 2 years ago
MODERATORS
I'm looking into Rust GUI libraries myself and playing around with Slint. I think it can use QT as a renderer, but I could be wrong.
Out of curiosity, any specific reason for QT as a requirement? It's certainly a good framework but I'm just wondering if there is anything specific for your use case.
Honestly, I just want to use whatever most of the native KDE Plasma apps use, and that mainly seems to be Qt. The other UI frameworks weren't as good or reliable afaik. Now that you mentioned Slint, I took a look at it, and it seems pretty solid.
Seems like Slint can use the Qt renderer: https://docs.slint.dev/latest/docs/slint/guide/backends-and-renderers/backends_and_renderers/#qt-renderer
I will check out Slint. Thank you.
If you are a company you should hire kdab to make their binding better, and maybe train you and whatever else they can do for you. There is a lot of friction between C++/QT (Which is very different from regular C++) and you will either spend your time fighting the friction of mixing languages, or you will hire someone else to worry about all those details while you focus on your problem.