An experimental Go cross platform UI library.
Unfortunately due to a shortage of hours in a day, GXUI is no longer maintained.
If you're looking for a GUI library for your next Go project, check out these alternatives.
The code is mostly undocumented, and is certainly not idiomatic Go.
This is not an official Google product (experimental or otherwise), it is just code that happens to be owned by Google.
In order to build GXUI on linux, you will need the following packages installed:
sudo apt-get install libxi-dev libxcursor-dev libxrandr-dev libxinerama-dev mesa-common-dev libgl1-mesa-dev libxxf86vm-dev
After setting up
GOPATH(see Go documentation), you can then fetch the GXUI library and its dependencies:
go get -u github.com/google/gxui/...
To build all samples run:
go install github.com/google/gxui/samples/...
And they will be built into
If you add
GOPATH/binto your PATH, you can simply type the name of a sample to run it. For example:
go get -u github.com/gopherjs/gopherjs go get -u -d -tags=js github.com/google/gxui/...
Afterwards, you can try the samples by running
gopherjs servecommand and opening http://localhost:8080/github.com/google/gxui/samples/ in a browser.
Many of the samples require a font to render text. The dark theme (and currently the only theme) uses
Roboto. This is built into the gxfont package.
Make sure to mention this font in any notices file distributed with your application.
GXUI was written by a couple of Googlers as an experiment and is now unmaintained.
Contributions, however small, will require the author to have signed the Google Individual Contributor License Agreement.
The CLA is necessary mainly because you own the copyright to your changes, even after your contribution becomes part of our codebase, so we need your permission to use and distribute your code. We also need to be sure of various other things—for instance that you'll tell us if you know that your code infringes on other people's patents. You don't have to sign the CLA until after you've submitted your code for review and a member has approved it, but you must do it before we can put your code into our codebase. Before you start working on a larger contribution, you should get in touch with us first through the issue tracker with your idea so that we can help out and possibly guide you. Coordinating up front makes it much easier to avoid frustration later on.