orbtk VS slint

i was gonna bring up https://github.com/redox-os/orbtk only to discover it's no longer under active development.

OrbTk is sunsetting in favor of Iced, slint, and future renderer-agnostic toolkits: https://github.com/redox-os/orbtk

Orbtk

The GitLab repo was deleted. You will need to update the submodule path to https://github.com/redox-os/orbtk.

That said, I'm not totally convinced about SixtyFPS today. There are some other interesting options that are suitable GUI toolkits for Rust. Such as OrbTk and Iced. Each toolkit is approaching the GUI space in a different way, so it'll be interesting to see where we end up in a few more years. QML-esque SixtyFPS, ECS-based OrbTk, Elm-based Iced, and a few others out there.

What's written in this article isn't the development of a GTK fork, but some reasoning for exploring alternatives to GTK. There aren't very many suitable candidates in this space, but Rust GUI toolkits like Iced have potential. Personally, I would add that OrbTk is also a suitable candidate.

I use orbtk, it is pretty easy to use, has an active dev team, works on windows mac and linux, and cross compiling from linux to windows is also easy with it. It is still pretty beta, but depending on the project you need it could work. (https://github.com/redox-os/orbtk)

Orbtk is an option. The default is backend is orbraq, which uses OrbClient. OrbClient will use SDL on Linux, and on Redox it should be a "pure" rust experience.

OrbTK recompiling stuff has been fixed in the development branch as far as I can tell: https://github.com/redox-os/orbtk/pull/409

OrbTK

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.