sixtyfps VS egui

As an anecdote, the three top contributors to sixtyfps are ex-Qt people. I think it is not anecdotal that there is at least some degree of overlap and competition between Rust and C++, and that this is a market that surely The Qt Company is watching.

SixtyFPS (https://sixtyfps.io/) is in progress for Rust, but it is still early days. It also does not technically use a native toolkit (it uses Qt), but I believe that might be on roadmap. For traditional GUI apps, I think the lack of a table or tree widget is the most limiting for the time being. They have stated they intend to remedy that.

The most promising GUI hasn't been posted here, SixtyFPS. It's in it's early stages and not FOSS, but it's built by some ex-QT cats and has a lot of potential.

People have been recommending https://sixtyfps.io/ to me.

There is already a project to make a Qt like GUI toolkit in Rust: https://sixtyfps.io/ It is really similar to Qt https://sixtyfps.io/releases/0.1.5/docs/rust/sixtyfps/index.html

People are doing that too. https://sixtyfps.io/ is basically a Qt clone in Rust, actually developed by previous Qt developers.

spdlog, a pretty useful and more and more commonly used logging library for C++.\ SixtyFPS, an emerging GUI library for Rust, but you can use it in multiple languages. It uses OpenGL or Qt currently as backend (well, it's a new library and they wanted two from the get-go to make sure their abstractions are done right/well enough). They started a company this year for it too.

Just so some are not aware, there's a new project called sixtyfps by some people who were in the Qt world for long. I didn't take a deep dive into it but it looks promising.

https://sixtyfps.io/ have a toolkit with Rust with free and paid offerings. I haven't used it, but might be worth the look.

As a beginner in GUI myself I would say that egui is a really good starter.

If you don’t mind just drawing into a rectangle (without native UI components), more options open up. There’s plenty of Rust libraries for just drawing into a buffer. Like https://github.com/emilk/egui, which does provide UI components, just not native one.

Besides a browser based GUI you have many other options like egui, Iced etc. In this case you can still use HTTP for communication between your programs, but also sockets, and, if the programs run on the same machine, named pipes and shared memory (which is more efficient for sharing big data chunks).

If you want to use separate codebases, then you might consider egui, iced or gtk-rs for the desktop part.

egui: this is technically a GUI framework, but it supports arbitrary rendering through a simple api, and you can also access the underlying graphics APIs if you want to. The eframe crate makes it easy to make an egui window.

A big thing keeping me on webview was accessibility - and with egui finally gaining AccessKit support, it spurred me into making some mockups, which I rather liked the look of.

I'd recommend giving egui a try: https://github.com/emilk/egui/. It aims to be very simple to use, and the repo contains several examples.

I've opened an issue! on Github.

The example is basically unchanged from 0.17 but now lives here: https://github.com/emilk/egui/tree/master/examples/custom_font