cosmic-comp VS keyboard-configurator

Maybe take a look at cosmic-comp it is currently in development by System76 for their own Cosmic DE. Smithay also has Anvil and Smallvil contained in it's repository, both are example implementations of a compositor using Smithay.

cosmic-comp

COSMIC DE isn't a singular thing, it's a project of several smaller projects being built on top of each other, like the cosmic-text project that'll be used for font rendering and this new cosmic-comp UI compositor project.

we have a lot of Rust projects of different scopes, but I am mostly working on cosmic-comp, a wayland compositor for our new upcoming Linux Desktop Environment. All Open-Source: https://github.com/pop-os/cosmic-comp

Thanks for the reply /u/mmstick. Also, would you know what causes this issue: https://github.com/pop-os/cosmic-comp/issues/28 I keep running into it when trying to compile cosmic-epoch

See https://github.com/pop-os/cosmic-comp

We hired the talent behind smithay, and cosmic-comp is based on it, which has been developed to the point where we have an early prototype with some functioning wayland-shell applets.

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