dialog VS giu

There is this: https://github.com/sqweek/dialog "Simple cross-platform dialog API for go-lang" Is that what you meant?

IMO if the file dialogs are your main problem with fyne, you could maybe combine it with another library or your own implementation to show native open/save dialogs instead, where supported. If you want to even go further, create a PR that integrates native dialogs into fyne (in addition to the custom dialogs that will still be necessary for consistency and fallback on systems without the necessary libs).

[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.