fltk-rs VS flutter_rust_bridge

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.

Use some sort of executable file, like webassembly. I've seen extism which is really cool. Though theres no dart port for it or a dart package, i think something could be done via flutter_rust_brige. This will allow people to use the languages supported via extism (js, go, rust, zig, cpp etc) to their full potential and have the language's ecosystem available and they can just compile the plugin to a wasm file and use it in the app. Downsides would be ig using that rust package in dart since flutter_rust_bridge does have some amount of complexity. And that for example, two plugins both written in say for example js, depend on some sort of http package, and both plugins load the same package twice in their respective wasm files. ig plugin files would be more larger in the end.

Not a Flutter Dev, but have you tried 'flutter_rust_bridge' [0]. Seems provide some interop between flutter and rust and looks like a popular and active project. I'm native mobile dev and just curious about this kind of interop myself. If it's seamless then looks like good balance to do mobile front-end in flutter and mobile backend in rust.

[0] https://github.com/fzyzcjy/flutter_rust_bridge

This template is primarily built using the flutter_rust_bridge library. It also incorporates several popular packages and modifications into the default Flutter template, ensuring optimal development process. It has been designed with future scalability and performance in mind.

If you want example code, the flutter_rust_bridge uses a webworker pool with shared memory on the web to multithread the execution.

There's also the thing that flutter_rust_bridge is currently broken for web development. I have a PR open, but it's running into weird issues with the CI and so can't be merged.

For reference, https://github.com/fzyzcjy/flutter_rust_bridge. And dart is a really nice language too, my only real gripe is that I'm no longer used to [type] [variable] over [variable]: [type]

https://github.com/fzyzcjy/flutter_rust_bridge (Fixed your href)

It appears that this is indeed what was happening. The issue has now been fixed in the template.