Relm4 VS dioxus

There is Relm (https://relm4.org/). Which is in Rust is just GTK (through it's Rust bindings) with a nice reactivity layer on top.

I’d recommend you checking out https://relm4.org if you know a little Rust. Relm4 is currently the easiest and most intuitive way to write GTK

Relm4 might make your migration easier. It has factories which make it easy to create lists (both sync and async) and recently added TypedListView as another useful abstraction over pure gtk-rs. There is a lot of potential in Rust + GTK, you just have to find idiomatic abstractions.

Did you try Relm? It's an implementation is the elm architecture (think react) on top of Gtk. Given your experience with Gtk it might suit you really well, as you can even take only parts of it and continue using bare Gtk for the rest. Give it a try!

What about relm4? Is it generally feature complete? Can one use relm4 for most things, and drop to gtk4 for the oddball task that is not supported?

https://relm4.org/

Using this example: https://github.com/Relm4/Relm4/blob/main/examples/simple.rs

What advantage would this Rust crate have over Relm4? It seems pretty similar to me, save for the property based syntax that Forte has, instead of the set_* ones used on Relm4.

If you like Rust I recommend Relm4, one of the best experiences I’ve had with a framework tbh, be sure to learn gtk-rs first.

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).

Floneum is a graph editor for local AI workflows. It uses llm to run large language models locally, egui, and dioxus for the frontend, and wasmtime for the plugin system. If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI