imgui-rs VS cargo-edit

there is a good bindings for imgui

There are rust bindings for Dear Imgui. It's a great immediate mode gui that has been used in the gaming industry for tooling. It supports floating windows and such. And there is a lot of customisability to be had. The benefit of the immediate mode gui is that it is constructed and rendered separately from the rest of the logic. Allowing you to build out whatever the gui is for, separately. Then, the gui can be removed from the final build if that is what you want.

Looks like the culprit is imgui-winit-support: https://github.com/imgui-rs/imgui-rs/pull/716

I am trying to use the imgui crate (along with imgui-winit-support and imgui-wgpu) with wgpu. I have followed the imgui-wgpu example and have gotten everything to work on the native version of the project.

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

Imgui, Imgui-rs

To move on to GUI dev, there's the Qt Framework, Eto.forms for C#; Rust has the ImGui wrapper for the C++ Dear ImGui library.

Have you looked into the imgui bindings for rust? imgui-rs

All the examples in the imgui repository use glium

“cargo add” from https://github.com/killercup/cargo-edit has that behavior, but not the built in one that was added to cargo

I have also noticed that the last commit of cargo-edit crate's GitHub repo (https://github.com/killercup/cargo-edit) was two days ago (pretty recent.) So it is probably relevant for a lot of people.

cargo-upgrade from cargo-edit (somewhat more intentional than builtin update)

I've also tried cargo-upgrade from cargo-edit like so:

You can also see how other crates do it. For example, cargo-edit is just like that - a single package with a library with a couple of small cli wrappers around it. You can compare their Cargo.toml to yours, maybe there is something different about them.

Just to check, are you aware of cargo-edit's cargo-set-version or cargo-release?

Speaking of cargo remove, see also cargo-edit [0] from which adding and removing originally came, as well as cargo-binstall [1] which installs binaries rather than compiling from source every time. The binaries are updatable with cargo-update [2].

The latter two can replace a package manager for Rust related utilities, as I often find that those in OS package repositories are often not as up to date as directly from cargo.

[0] https://github.com/killercup/cargo-edit

[1] https://github.com/cargo-bins/cargo-binstall

[2] https://github.com/nabijaczleweli/cargo-update

For context, it was/is part of cargo-edit crate which provides other nice functionalities as well. Hope all gets integrated in time.

https://github.com/killercup/cargo-edit can use the F option