Slint 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.

Thank you for linking your project—that looks really cool! I saw you also implemented a pan-and-zoom area. We are currently working on moving Rerun's implementation to egui [0], so maybe keep an eye on that.

It would be super cool to have layered graph drawing in (Sugiyama-style) in Rerun too. The tricky–but super interesting–challenge that we face is that our layout implementations need to be consistent across timestamps if the underlying structure of the graph changes, which is why we initially chose a force-based layout approach. There, the time-varying aspect is handled naturally by the simulation.

The very interactive nature of Rerun also poses more restrictions on the implementation of our algorithms: re-layouts ideally need to be fast, to produce visualizations quickly, especially when scrubbing the timeline.

I still hope we can rid you of some of the todos ;).

[0](https://github.com/emilk/egui/pull/5505)

Yeah, I knew I was in for some onoz when I saw "compiled to WebAssembly and rendered with WebGL". In their defense, it's stunning that any text operations work at all

Also, "There is no DOM, HTML, JS or CSS" is some uh-huh given the considerable amount of silliness involved in view-source:https://www.egui.rs/

One of these projects, which is built using Rust, is egui. In this article, we’ll see how we can build a simple, cross-platform GUI application with it.

Cross-platform UI development is a total mess with literally zero solutions ticking all the boxes.

If you want to write an app which will target all the major platforms (3 desktops and two mobiles), want a native look and minimal effort for every platform you target, there is nothing apart from QT.

If you drop native look requirement, some small things like https://www.egui.rs/ might work for you.

If you drop the minimal effort requirement, all the webivew based mess might help you but it won't be easy due to multiple reasons.

It allow to edit large json files > 500mb. It is written in rust and use the amazing egui library