haven/nexgb
Andrew Gallant (Ocelot) 39507f86ab finally starting on the crescendo: requests and replies. 2012-05-02 01:46:30 -04:00
..
xgbgen finally starting on the crescendo: requests and replies. 2012-05-02 01:46:30 -04:00
.gitignore last commit before i tear everything down 2012-04-29 14:09:03 -04:00
AUTHORS initial commit. not currently in a working state. 2012-04-28 23:25:57 -04:00
CONTRIBUTORS initial commit. not currently in a working state. 2012-04-28 23:25:57 -04:00
LICENSE initial commit. not currently in a working state. 2012-04-28 23:25:57 -04:00
Makefile initial commit. not currently in a working state. 2012-04-28 23:25:57 -04:00
README float my boat 2012-05-01 01:09:45 -04:00
auth.go initial commit. not currently in a working state. 2012-04-28 23:25:57 -04:00
xgb.go progress. still not working. this is incredibly difficult. 2012-04-29 03:38:29 -04:00
xgb_help.go progress. still not working. this is incredibly difficult. 2012-04-29 03:38:29 -04:00

README

BurntSushi's Fork
=================
I've forked the XGB repository from Google Code due to inactivty upstream.

Much of the code has been rewritten in an effort to support thread safety
and multiple extensions. Namely, go_client.py has been thrown away in favor
of an xgbgen package.

The biggest parts that *haven't* been rewritten by me are the connection and
authentication handshakes. They're inherently messy, and there's really no
reason to re-work them.

I like to release my code under the WTFPL, but since I'm starting with someone
else's work, I'm leaving the original license/contributor/author information
in tact.

I suppose I can legitimately release xgbgen under the WTFPL. To be fair, it is
at least as complex as XGB itself. *sigh*

What follows is the original README:

XGB README
==========
XGB is the X protocol Go language Binding.

It is the Go equivalent of XCB, the X protocol C-language Binding
(http://xcb.freedesktop.org/).

Unless otherwise noted, the XGB source files are distributed
under the BSD-style license found in the LICENSE file.

Contributions should follow the same procedure as for the Go project:
http://golang.org/doc/contribute.html