piet VS orbtk

You can even check https://github.com/linebender/piet and https://github.com/RazrFalcon/tiny-skia. They are pure rust libraries. Skia as a whole is a big binary to add.

First, at the deepest level, we are moving away from Piet, which is a cross-platform 2D graphics abstraction. Under the hood it uses whatever the standard OS API is. Instead we will be using Vello which we have been building as a research project for years already. It is starting to near its v0.1, which is very exciting. Fundamentally it is a novel GPU accelerated 2D rendering engine with a strong focus on performance. It is not ready for benchmarks yet, but we're confident it will deliver. If you're curious, you can check out the Vello roadmap for 2023.

you can use piet, although that is more of an abstraction over existing, platform-dependent libraries. So not really pure rust, but definitely cross-platform.

Piet is the backend for the Druid UI framework. It is indeed cross-platform. The SVG backend looks like it would work without an OS, but I'm not sure the value of a GUI toolkit without an OS anyway :)

https://github.com/linebender/piet#backends

https://github.com/linebender/druid/tree/master/druid-shell/...

Piet can render text. You can use Piet_common with the BitMapTarget to generate images Here is an example.

Piet (https://github.com/linebender/piet) should work.

So the 3 I'm looking at right now are 1. druid 1. piet 1. bevy

It relies on piet 2D graphic library; on Linux that means GTK/Cairo 2D primitives

You may be interested in taking a look at piet!

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