atk VS walk

You might want to look at github.com/visualfc/atk. Tk is a toolkit traditionally considered unsexy but it is 1) rock solid 2) cross platform, while using native Win32 API to render its widgets.

I think interp layer of atk is a good entry point for minimal API. Then you can reuse higher level API of atk and check by demo.

For creating simple desktop apps for (mostly) my own use, the ones I found working best for me where two binding to existing ui toolkits: - Tk: https://github.com/visualfc/atk - and a small custom wrapper around fltk I've written Both have some issues, but e.g. fyne and some of the immediate mode ui's I've looked at where lacking some features, and I couldn't build therecipe/qt (I don't event know if it's still maintained).

Fyne is just really ugly for me.. I'm trying to learn more about GIO lately (gioui.org) which seems to have a great potential. However you request is very simple: native Windows Gui. And there are few libraries for that: - https://github.com/gonutz/wui - https://github.com/lxn/walk - https://github.com/tadvi/winc - https://github.com/rodrigocfd/windigo

walk https://github.com/lxn/walk

My experience with gui in golang is pretty bad. I took a project which used https://github.com/lxn/walk , and unfortunately the library doesn't have a good documentation. So I had to figure out a whole lot of things by looking into example snippets or via hit and trial. Moreover, it's platform specific. So yeah wasn't a good deal. By the way, if you are thinking of targetting cross-platform then some HTML based GUI library would be much better choice.

Look at https://github.com/lxn/walk. While it offers a cgo optimization for the event loop, I don’t believe it’s required.