fltk-rs VS egui

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.

Work on the fltk-rs wiki. Maybe a book can come out of it.

egui (https://github.com/emilk/egui)

A simple TextEdit window with content being added from the bottom becomes blurry. What actually happens is that, at 60 FPS, alternate frames are displaced upwards slightly. A 30 FPS video capture looks fine, but a 60 FPS capture shows the problem. This worked in previous versions of egii, but is broken in 0.21.0. This may be related to a generic problem with "bottom up" mode in the layout engine. Egui has one-pass layout, done on each frame, but tries to do some things which are hard to do in one pass.

You could make the screenshot lovers very happy by adding some directly to both your Readme (I know there are some in the wiki) and to https://github.com/emilk/egui/issues/996

egui is excellent and runs in any browser that supports wasm.

Not true, even if you add Rust. egui was released earlier: https://github.com/emilk/egui

And egui isn't tied to Apple proprietary frameworks.

All that talk was about declarative UI approaches; on the other side there are Immediate-mode UIs that redraw everything several times per second, and work well enough with things like game engines. In that regard I believe https://github.com/emilk/egui/ is good enough for now.

I started trying to port the UI to egui, but gave up pretty quickly after realizing that it doesn't have a particularly good way to customize the style of widgets so it'd probably be pretty hard to get everything looking the way I wanted it to.

Concerning GUI frameworks, the most common ones are druid, egui and iced. All three of them run native and on the Web.

With that said there's nothing as mature as Qt in pure Rust. If you want something really mature and stable, and you don't mind TypeScript, you should probably look at Tauri. Otherwise egui is nice, but there are other alternatives.