[go-nuts] GUI - Current cross-platform GUIs, Graphics for Go?

gowut:
http://code.google.com/p/gowut/

+ forgot to add this one:

*CEF2go*
https://github.com/CzarekTomczak/cef2go
CEF2go is an HTML 5 based GUI toolkit for the Go language. (CEF = Chromium
Embedded Framework)

+

*GosGL*
https://github.com/phaikawl/gosgl

*OpenVG*
https://github.com/ajstarks/openvg

*NanoVG*
https://github.com/memononen/nanovg

AFAIK, go-qml is used in Lime https://github.com/limetext/lime
(the supposedly opensource implementation of SublimeText).

Gothic is simple and effective

Gowut is missing, http://code.google.com/p/gowut/

My dream for Go is to be small, clean language with simple syntax and
not language cluttered with ballast of such nonsense as the default and
cross platform GUI library (and many other nonsensical ballast).

Libraries are for such things. And there are many libraries for
different 'things' despite the fact that the language is still young.
[...]

I wasn't suggesting a GUI for Go's default packages.

*Even so, responding hypothetically:*

Go is entirely comprised of libraries. Your point is moot. The beauty of Go
is enduring, simple syntax. Bloat, in the way you're likely inferring, is
mostly nonexistent until you intentionally invite it into *your* code. If
you haven't, please familiarize yourself with the default source
<https://code.google.com/p/go/source/browse?repo=default>. Additional
repositories such as crypto
<https://code.google.com/p/go/source/browse?repo=crypto>, net
<https://code.google.com/p/go/source/browse?repo=net>, and even image
<https://code.google.com/p/go/source/browse?repo=image> are in an
experimental state. Some parts may come to the default in time. Some parts
will not. It's a healthy process mostly. *If*, hypothetically, GUI
standards became more officiated, it wouldn't affect you. If you think
otherwise, then a great number of highly useful things that currently exist
in Go -- *HTTP library, text/html templates, pluggable database standards*,
and on -- must negatively affect you. You should consider that bloat. One
person's "bloat" in this hypothetical sense is another person's treasure,
making an entire language lauded with great praise for its robust, growing
libraries -- such as the case in Go.

You may feel that cross-platform GUI libraries are "nonsensical ballast."
Conversely, you might of meant this in the context of misunderstanding.
That statement, nevertheless, seems to hint at a very insensitive disregard
to the great number of people who develop, use, and enjoy graphical
interfaces. That's nearly ever person who uses a computer. GUI libraries or
standards thereof are no less "nonsensical ballast" than many other
conveniences. I'll reiterate. No one's suggesting a GUI in the default
standards. In whatever form it exists, it may be every bit as welcomed and
prosperous to Go.

The impact of a robust GUI framework in Go would be astronomically positive
to the future of Go. It would likewise be extremely positive to Linux. I
care about this. I'm witnessing developers, newer and older generations
alike, finally shifting to Linux as a result of their love of Go and Go
projects surrounding it. It's been a breath of fresh air to me. The
momentum would be phenomenal over a GUI in Go.

----

Thank you for additional links and thoughts.

There are CLI applications, and web applications*. Cross-platform "GUI" libraries are relics of a bygone era**.

* Or "hybrid" which is embedded web.
** Ultimately, users don't care for cross-platform applications- they just want something that /feels/ native on /their/ platform.

Hundreds of millions of people who develop with and benefit from Qt, Gtk+,
Tcl/Tk, WxWidgets, Juce, Marmalade, Xamarin, Java/Swing, and many other
cross-platform libraries completely disagree with you. The number is
probably 1-2 billion users across all popular software, easily over half of
the world's computer users.

just want something that /feels/ native on /their/ platform.

Many types of cross-platform frameworks exist. Some directly target native
controls. Some are strictly unified. Others are a mix. My experience is
that users care about software that's good, fast, and has helpful UI.
Anything unified but properly extendable can simulate nearly any
environment. It's also my experience that most users (Windows users as an
example) don't care or know if their programs are made via Qt or WPF &
WinForms, as long the end result is *good*. If you don't even see the value
in current cross-platform GUIs in C, C++, C#, and on, then I especially
won't try to convince you.

You are giving advice to someone who finished this journey two years
ago, at least and someone who follows Go from when it is announced
publicly first time.
I think the developers switch to Linux because of the 'Linux ecosystem'
and sharing culture (and quality, of course) and not just because of
one programming language.

Finished? As you have, I've been with Go since its beginning. I'm an active
participant in FOSS in general but, of course, my perspective is always my
own. Go has been unifying. I've seen it shuffle many people into Linux once
v1 hit. Docker and several other projects that use Go are greatly fueling
this momentum. The bigger momentum is that Go is approachable and has solid
libraries. It feels self-evident to say but, so it goes, there have been
many people formerly stuck in the lands of Python, PHP, RoR, Java, and .NET
who were suddenly able to find a home in Go: a home highly conducive to
Linux (*in my view*). Meanwhile, a large portion of the C-crowd simply
carried on, likely already using Linux. I'm grateful either way.

+
*gotk3*
https://github.com/conformal/gotk3/

W dniu piątek, 12 września 2014 19:32:30 UTC+2 użytkownik wormra napisał: