zenity VS atk

I created github.com/ncruces/zenity and I'd welcome ports to either D-Bus Portal or KDialog.

I've used the windows version pretty extensively in github.com/ncruces/zenity to generate this.

You can see it in… “action” in some of my repos: - github.com/ncruces/go-strftime - github.com/ncruces/go-sqlite3 - github.com/ncruces/zenity

Const errors are totally doable. https://dave.cheney.net/2016/04/07/constant-errors https://github.com/ncruces/zenity/blob/master/internal/zenutil/env.go

If you use a non-native GUI, you can still leverage native dialog windows via https://github.com/ncruces/zenity

To add a calendar dialog to github.com/ncruces/zenity, I needed a strftime implementation in pure Go.

github.com/ncruces/zenity

I've been working on a "port" of it to macOS and Windows, that doesn't require X. It also works on WSL (as well as Cygwin/MSYS2 and Git for Windows). It's on GitHub: github.com/ncruces/zenity.

Started out with just the file and message dialogs, but a lot more of zenity has been wrapped/ported, current status: here.

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