Slint is pretty much the spiritual successor to QtQuick. I think it’s written by people that used to work for Qt, it has a similar design (GUI focused DSL with automatic reactivity), and they are even using the same business model - basically free except for embedded use (cars, petrol pumps, PoS etc.). But without the decades of baggage Qt has and with support for Rust from day one.
It can even use Qt as a backend somehow.
I had a go with Slint because it does look impressive but tbh the amount of setup you have to do is just a bit too much compared to something like gpui-component. Probably worth it for a bit project I guess.
Well yeah, but I would want to use Qt/QML to have native integration with something like KDE Plasma.
Unfortunately Slint just recently announced that they will be slowly deprecating the native styles except Fluent, which is Windows’s useless and unused style: https://slint.dev/blog/default-native-style-change
So it is quite good to have this Qt Bridge for Rust.
Yeah that part from them was very disappointing. I was really hoping for the qt style integration to be maintained. I really want to do something that integrates well in our plasma/kde environments but don’t want to touch those weird languages to do it.
Hoping this new approach from qt is successful. They tried to maintain others like qt jambi but that is kinda of abandoned or wtv.
What work?
Slint is pretty much the spiritual successor to QtQuick. I think it’s written by people that used to work for Qt, it has a similar design (GUI focused DSL with automatic reactivity), and they are even using the same business model - basically free except for embedded use (cars, petrol pumps, PoS etc.). But without the decades of baggage Qt has and with support for Rust from day one.
It can even use Qt as a backend somehow.
I had a go with Slint because it does look impressive but tbh the amount of setup you have to do is just a bit too much compared to something like gpui-component. Probably worth it for a bit project I guess.
Being rust native with a ui language like qml and showing all their things working with 3 or 4 languages every release.
Well yeah, but I would want to use Qt/QML to have native integration with something like KDE Plasma.
Unfortunately Slint just recently announced that they will be slowly deprecating the native styles except Fluent, which is Windows’s useless and unused style: https://slint.dev/blog/default-native-style-change
So it is quite good to have this Qt Bridge for Rust.
Yeah that part from them was very disappointing. I was really hoping for the qt style integration to be maintained. I really want to do something that integrates well in our plasma/kde environments but don’t want to touch those weird languages to do it.
Hoping this new approach from qt is successful. They tried to maintain others like qt jambi but that is kinda of abandoned or wtv.