Relm4 VS tealr

Relm4 is the newer version for GTK4 https://github.com/AaronErhardt/relm4

[dependencies.relm4] git = "https://github.com/AaronErhardt/relm4" branch = "new-approach" [dependencies.relm4-macros] git = "https://github.com/AaronErhardt/relm4" branch = "new-approach"

Probably, many gtk-rs devs have used C before and also GObjects can give you more control in some cases. But for the most part you will be fine using idiomatic Rust with something like Relm4.

As for writing apps, I've been enjoying Rust + Relm4 (https://github.com/AaronErhardt/relm4), but it might be easier to start off with Python or Vala and GTK or similar. A lot of gnome apps are Python. This looks like a good way to get started: https://www.gtk.org/docs/language-bindings/python/

relm4 - like relm, but for GTK4

Creator of [Relm4](https://github.com/AaronErhardt/relm4 here. Of course I might be a bit biased but I honestly think Relm4 has currently the best cross-platform and full-featured GUI experience for Rust programmers :)

I'm working on relm4, an new version of relm using gtk4-rs

working more on tealr more specifically tealr_doc_gen

Fixing some short comings in tealr that people discovered. Also, making hv_lua work with tealr and ideally start adding that fishfight.

Fantastic! Very happy to see this move forward at such a fast pace. We’re implementing scripting in Fish Fight via the tealr crate, which wraps mlua (and rlua).

Hopefully the last hand on https://github.com/lenscas/tealr for a new release. Mostly going over the documentation. Laying less emphasis on teal and more on "Hey, using this you can express a more typesafe api to lua and can actually easily document it.".

tealr, my wrapper around rlua and mlua to focus on (among other things) being better able to describe your api in the form of types: Getting it to a point to release a new version. Which is all about allowing people to document they API that they created for lua/teal. This documentation gets written to the definition files when generating them. In addition, you can also ask tealr to generate a instance.help(page:Option) method on your types. When doing this, the documentation gets made available through this function. By default it prints out "type level" documentation for this type, as well as what other pages are availalbe. When given a string, it shows the documentation for that page instead. Pages that belong to methods also automatically include the type signature.

This requires some new features in my Rust <-> Teal FFI library tealr https://github.com/lenscas/tealr which is now also close to getting a new release, with the only thing I want to do is fix how its TypedFunction work (right now, it always contains a lua function, even if it was made inside of Rust, which puts some needless limits on it).

After that it is time to finish mlua support for tealr . As well as making it better at dealing with api's like tealsql has made.

In case anyone is interested: Issue about it here https://github.com/lenscas/tealr/issues/17

Can you try removing the println! at https://github.com/lenscas/tealr/blob/cee2363a14c53b995a69efb2b4cbd84010905276/tealr_derive/src/lib.rs#L155?