orbtk VS cargo-edit

i was gonna bring up https://github.com/redox-os/orbtk only to discover it's no longer under active development.

OrbTk is sunsetting in favor of Iced, slint, and future renderer-agnostic toolkits: https://github.com/redox-os/orbtk

Orbtk

The GitLab repo was deleted. You will need to update the submodule path to https://github.com/redox-os/orbtk.

That said, I'm not totally convinced about SixtyFPS today. There are some other interesting options that are suitable GUI toolkits for Rust. Such as OrbTk and Iced. Each toolkit is approaching the GUI space in a different way, so it'll be interesting to see where we end up in a few more years. QML-esque SixtyFPS, ECS-based OrbTk, Elm-based Iced, and a few others out there.

What's written in this article isn't the development of a GTK fork, but some reasoning for exploring alternatives to GTK. There aren't very many suitable candidates in this space, but Rust GUI toolkits like Iced have potential. Personally, I would add that OrbTk is also a suitable candidate.

I use orbtk, it is pretty easy to use, has an active dev team, works on windows mac and linux, and cross compiling from linux to windows is also easy with it. It is still pretty beta, but depending on the project you need it could work. (https://github.com/redox-os/orbtk)

Orbtk is an option. The default is backend is orbraq, which uses OrbClient. OrbClient will use SDL on Linux, and on Redox it should be a "pure" rust experience.

OrbTK recompiling stuff has been fixed in the development branch as far as I can tell: https://github.com/redox-os/orbtk/pull/409

OrbTK

“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