gtk-rs VS gdnative

gtk-rs

GTK: I have little - no experience with GTK, and from what i have read it is cross-platform similar to wxWidgets, however is an emulated UI system similar to Qt. As i have no experience with it i am not sure how well supported this library is as far as it's Rust - bindings are concerned gtk-rs

In a gtk-rs application, I'm running a xdotool command to get the id of the application's window. I'm running the command in a connect_show closure (after the window has been shown):

To build the UI, I used gtk-rs. My experience with this library was quite pleasant; it was easy to use and there were a lot of examples. However, it isn't as widely used as, say, React, so it was difficult to find answer on Stack Overflow (I come from a JavaScript/Typescript background).

I'm using x11rb to interact with a window created with gtk-rs. window_id is the ID of the window created with gtk-rs. window_id_2 is the ID of the window created with x11rb (for testing purposes).

I haven't used it yet, but gtk-rs looks pretty good too. I've used GTK in general, just not the Rust bindings so far. The tutorials seem nice and GTK is a good UI toolkit overall.

I'm using gtk-rs. I want to trigger some code after the window has been shown (has displayed on the screen):

I'm using gtk-rs to add ListBoxRow items to a ListBox. The items are successfully added if I do it outside of input.connect_changed, a closure. But nothing is added if I do it from inside input.connect_changed:

For GTK, there's https://gtk-rs.org/

Out there there are already some open source projects trying to do this, but most of them are abandoned or in a very alpha stage. The most promising project so far seems to me git-kt. This project is trying to do something similar to what gtk-rs does for Rust, which is using GObject Introspection (GIR) files to generate Kotlin native bindings automatically.

It's a little less standard use, but Godot has been used to build application guis, which could be paired with rust bindings to implement app logic. I can't speak to reproducibility/scalability, but Godot's ui is extremely solid, and I'd probably choose that over Bevy until Bevy's ui progress matures.

Adding onto this, I successfully written a game in Godot using gdnative / gdext. I started with a split approach using gdscript and rust for CPU intensive but found that the API layer was slow at transferring large amounts of data (serialization?). I ended up rewriting it in all rust and it worked like a charm. I was able to target native and web assembly, the web assembly was much slower but worked on the browser.

Check this: https://github.com/tomuxmon/bevy_roguelike if you are still into bevy. Scheduling is a bit bork and I have not found time to port it to latest bevy. But most of the systems should work fine(if used on latest bevy). But again. If you want faster result go with something like Godot. In fact, just go with Godot. It is mature, easy to start, no lock in(free and MIT license), a lot of learning material. Also with Godot you can also use Rust https://godot-rust.github.io/. Ditch Unity (do not have time to explain 😅). Have fun!

Bevy Godot-Rust

> Same for Godot.

While likely true that it's "Unlikely to ever be as supported" as the 4 officially supported languages[0] ("GDScript, C#, and, via its GDExtension technology, C and C++."), Godot's GDExtension technology is specifically intended for use in adding support for other languages.

The most relevant tracking issue for Rust is presumably:

* <https://github.com/godot-rust/gdnative/issues/824>

Which links to:

* <https://github.com/godot-rust/gdextension>

[0] https://docs.godotengine.org/en/4.0/getting_started/step_by_...

...Godot v3.x has Rust support via godot-rust and Godot v4.0 is released as of this month?

I was curious, and looked it up. Nothing built in, but there's an interesting project that works with godot: https://godot-rust.github.io/

There's people working on it: https://godot-rust.github.io/