fyne VS giu

If you want to look at something a bit bigger I can also suggest looking at Fyne (the toolkit that I’m working on and using to build the app): https://github.com/fyne-io/fyne

Tauri is definitely a hot SEO keyword!

I had not heard of https://wails.io before for Golang GUIs, only https://fyne.io which renders its own controls.

And this is how https://github.com/go-gst/go-gst, https://github.com/go-gl/glfw, and even https://fyne.io/ are using system libraries to propose a lot of functionalities.

It would be great if we could add support for Flatpak portals in https://github.com/fyne-io/fyne but I find the portal documentation complicated (especially if preferring to use D-Bus instead of accessing libportal using C). Does anyone have code examples for using portals from Go code?

If you fancy Go, there's Fyne. I don't work in the space so I cannot judge it.

https://github.com/fyne-io/fyne

[https://github.com/allendang/giu

I prefer giu + zenity for tooling GUIs with either very few or very many elements (i.e. 100's). I use Flutter for when I want an attractive GUI of medium complexity.

FYI, they're using Dear ImGui. Either https://github.com/AllenDang/giu or https://github.com/inkyblackness/imgui-go

I did poke around for a bit, but I really needed the tool, and I knew it would be days of work if I learned a new tool and hours if I stuck with what I knew.

My coworker Andrew did start a similar tool, which is here: https://github.com/andrewpmartinez/grid and uses https://github.com/AllenDang/giu for the UI.

Next time I need a feature I probably take a look at that and see what the model looks like and and how straightforward it is to work with.

To maintain my another GUI lib giu (https://github.com/AllenDang/giu), I used to update imgui manually time to time, and it always a pain in my ass.

I then used GIU (https://github.com/AllenDang/giu) which is a Go wrapper around IMGUI - I found major performance issues since my requirements are pretty extreme, I was plotting charts containing 1000's of points and the overhead of calling the underlying C libraries from Go was too much.