fltk-rs VS rfd

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.

Finally, if you’re not familiar with a front end javascript library—maybe because you’re a backend developer—You might also want to look into libraries for programming languages that you’re familiar with. There are often wrappers for existing technologies like GTK, FLTK, Qt. For example, FLTK-rs for Rust, or the GTK3 gem for Ruby.

Sure, thanks for the suggestions. I initially thought this would be a generic issue that didn't need much context, I now see that's not the case... I also like to think about this particular code as a "block". The block has to open a file and call self.reset(&code). Therefore, I don't have a particular commit with an issue, the code itself (which I basically copied from the rfd example has the issue...

Here's the github link https://github.com/polymeilex/rfd

If you run into issues, please report them on the issue tracker.

I used this to contribute a backend for rfd so you can have cross platform native file dialogs without depending on GTK on Linux.

I haven't yet used the dbus crate but I was thinking of doing so soon for https://github.com/PolyMeilex/rfd/issues/36. Could you elaborate what bothered you about the dbus crate and why you think zbus is nicer to use?