… well, I decided to use QT productive now. At first I had made some little experiments with go-QT and go-GTK and go-GTK3. In past I liked to use WxWidgets and GTK with Python and didn’t like QT so much. For me, QT was oversized and I loved Glade & wxGlade-Builder very much. However I have to write several Process-Visualization-Screens, which must work on Win7 
and Win10 
, but running on Linux 
is also intended.
At the moment, QT seems to be the only GUI framework that is mature enough to run on multiple systems without major configuration overhead! Unfortunately, go-GTK is not that mature and even more problematic under Windows. But I can not deny that cross-compiling with QT causes me some headaches. And I also had many problems (not solved yed!) compiling go-QT directly on Win7_32bit. Docker seems to be the most comfortable way to develop my application under Linux, but to roll it out on any Windows. At least, I’m so confident now that related issues are always somehow solvable.
The other alternative would have been e.g. the design of Screens with JavaScript-jQuery-EasyUI etc. frameworks, as everyone is doing right now. But I do not like to compensate performance deficits by massive memory consumption and tons of dependencies.
One thing is really good with QT: It has proven to be sufficiently practical to translate code examples from Qt Widgets 5.11 for Go, which indirectly makes the documentation status very good. And then you should always have a look at GitHub - therecipe/examples: Examples for https://github.com/therecipe/qt .
Incidentally, Home · tomarus/go-gui-libs Wiki · GitHub provides a very nice overview of the currently possible visualization techniques in Go!