fltk-rs VS keyboard-configurator

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.

Many or most of their keyboards are configurable these days. See https://github.com/pop-os/keyboard-configurator

Reported at https://github.com/pop-os/keyboard-configurator/issues/195 - I get a failure from dfu-programmer trying to update using the alternate update method with the keyboard-configurator app (because fwupdmgr won't update it because of the firmware bug that the new firmware addresses).

I found the ticket regarding Fn lock https://github.com/pop-os/keyboard-configurator/issues/159

keyboard-configurator

Good. I bought Darter Pro recently and had to - business as usual under Linux - compile this and tweak that. Via things like their keyboard configurator[1] I was exposed me to Rust's GTK bindings. It wasn't pretty: the mismatch between the obviously object-oriented GTK and Rust which doesn't do (and doesn't want to) OOP was glaring. I understand the appeal of Rust very well, and I'm happy they write their drivers and (parts of) firmware in it, but it's about as fit for OOP-based GUI as Go and Erlang. Which is to say - not very much.

[1] https://github.com/pop-os/keyboard-configurator

That's exactly what it's meant for, but the frontend of the configurator app doesn't seem to list those characters. You may consider opening an issue and relating to this one: https://github.com/pop-os/keyboard-configurator/issues/105

Probably a good issue to open here: https://github.com/pop-os/keyboard-configurator