slint VS cxx-qt

Did you get a chance to check https://slint.dev?

Disclaimer: I work for Slint

Currently, we do it by using binaries through napi-rs so we can bring in a window using the platform native API. And then we do some hack to merge the event loops.

But if Deno supports bringing up a window directly, this means we can just ship wasm instead of native binary for all platform. And also I hope event loop integration will be simplified.

Although we'd also need more API than just showing a window (mouse and keyboard input, accessibility, popup window, system tray, ...)

[1] https://slint.dev

Rich Text content is not yet implemented. This is tracked in https://github.com/slint-ui/slint/issues/2723

Thanks for reporting the broken link. Fixed in https://github.com/slint-ui/slint/commit/9200480b532f49007d2...

With Slint (https://slint.dev) we're trying to make a lightweight toolkit that doesn't use HTML/CSS. And that you can program either from low level languages such as C++ or Rust. As well as with higher level language such as JavaScript, and we want to extend to python too.

I haven't. I was just searching for a GUI library that was Bevy-compatible and slint isn't at the moment: https://github.com/slint-ui/slint/discussions/940

Sorry!

Trying to do that with Slint: https://slint.dev

You can do that with Slint (https://slint.dev) and its linuxkms backend. No need for a xorg server or wayland compositor, just run the application made with Slint from the init script.

My employer, KDAB, is building an excellent Rust binding for Qt: https://github.com/KDAB/cxx-qt

You can use cxx-qt or qmetaobject-rs. Or use Slint

Rust has several Qt bindings. The most popular are Ritual, CXX-Qt, and qmetaobject. Ritual is not maintained anymore, and qmetaobject doesn't support QWidgets. So CXX-Qt is our best bet for now.

Qt bindings for Rust also exist, although I'm not sure how mature they are: https://github.com/KDAB/cxx-qt/

We're getting closer, but you're still likely to run into missing features in CXX-Qt at this point. If you do, please report it on GitHub!

This is no longer required in CXX-Qt as of this week (https://github.com/KDAB/cxx-qt/pull/428). Next release coming soon.

From my understanding KDAB isn't trying to "replace" Qt. They're working on cxx-qt to make using Qt and Rust together much easier.

I second this. I wrote an internal Qt/QML app that ran on Windows, Linux, Android, and Raspberry Pis. We had ~20 Raspberry Pi's running this app in kiosk mode. If only KDAB/cxx-qt[1] were ready there, I would have done as much as possible in rust .

- [1] https://github.com/KDAB/cxx-qt/