fltk-rs VS dioxus

I have added a tile example to the repo, it's based on the FLTK example.

fltk-accesskit is an accesskit integration crate for fltk-rs, the gui crate. It's implemented as an external crate to allow for more experimentation before stabilizing the api, especially since fltk is at version 1.4.

fltk-rs worked well for me, for a small app.

Gtk doesn’t require you to write xml, you can write your gui code in Rust. You also have https://github.com/fltk-rs/fltk-rs

Currently, I have narrowed potential libraries to: 1. Flutter 2. FLTK 3. Relm (GTK) 4. iced 5. Slint 6. Imgui, Imgui-rs 7. and gtk-rs

FLTK

The fltk-rs library provides Rust bindings for the FLTK toolkit. The fltk-rs crate supports old architecture with more than 80 customizable widgets and more than four supported theme schemes, including the GTK scheme. You can also use the fltk-theme crate for more customizations.

A friend of mine grew tired of plotting libraries that did not allow adding data points to his plot interactively like you can in Matlab, so he wrote one using FLTK using C++. I refactored his code a bit and then ported to Rust using the fltk-rs crate. Recently I needed this library for a project and I noticed I had not made it publicly available on Github. So I present to you the fltk-plot library!

fltk-rs is a Rust bindings crate for FLTK, the cross-platfrom & lightweight gui library.

Besides GTK I can recommend FLTK. It has been around for a long time and is very stable.

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