haven - Haven is an umbrella project for a range of mostly desktop applications

	Commit message (Collapse)	Author	Age	Files	Lines
*	Export the logger (again)	Axel Wagner	2018-09-08	1	-12/+16
\| \| \| \| \| \| \| \|	Just enabling or disabling logging falls short of the power of interfaces of go. A user is forced to either accept the logging to stderr in the format defined by xgb or disable logging alltogether. By exporting the logger, we can actually let the user decide where to log in what format.
*	Fixed a nasty bug where closing could cause ReadFull to crash	Andrew Gallant	2018-09-08	1	-11/+29
\| \| \| \|	the program. Close #4.
*	gofmt	Andrew Gallant	2018-09-08	1	-12/+12
\|
*	Provide access to the X display number in the XGB Conn.	Andrew Gallant	2018-09-08	1	-0/+1
\|
*	The hack continues. I've increased the event channel buffer. I know I'm	Andrew Gallant (Ocelot)	2018-09-08	1	-1/+2
\| \| \| \| \| \| \| \|	goofing here. What I'd personally like to do is just use an "infinite" channel. That is, push the limit of how many events can be processed to the machine and not set an artificial limit in XGB. Some day...
*	Doc fixes and stop exporting ReplyChecked and ReplyUnchecked	Andrew Gallant (Ocelot)	2018-09-08	1	-1/+15
\|
*	Doc touchups.	Andrew Gallant (Ocelot)	2012-05-26	1	-9/+14
\|
*	Add new logger type so that it can be shut off.	Andrew Gallant (Ocelot)	2012-05-16	1	-15/+13
\|
*	export logger so it can be disabled	Andrew Gallant (Ocelot)	2012-05-16	1	-13/+13
\|
*	close channels.	Andrew Gallant (Ocelot)	2012-05-12	1	-1/+13
\|
*	A more idiomatic way of trying a non-blocking send on a buffered channel	Andrew Gallant (Ocelot)	2012-05-12	1	-3/+5
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	and falling back to a blocking send inside a goroutine. This really needs to be fixed. The situation only arises when events are sent and aren't pulled off the channel using {Wait,Poll}ForEvent. Namely, if the event send blocks, the entire program will deadlock. Using a goroutine is not ideal because we lose a guarantee of order: that events are processed in the order of their arrival. However, it seems OK as a temporary band-aide for a situation that probably doesn't arise too often. What I need to do is implement a dynamic queue. Here is a reference implementation: http://play.golang.org/p/AiHBsxTFpj
*	docs	Andrew Gallant (Ocelot)	2012-05-12	1	-2/+5
\|
*	better docs	Andrew Gallant (Ocelot)	2012-05-10	1	-2/+0
\|
*	a huge commit. splitting extensions into their own sub-packages.	Andrew Gallant (Ocelot)	2012-05-10	1	-38/+51
\|
*	make resource ids their own individual types. last commit before overhaul to ↵	Andrew Gallant (Ocelot)	2012-05-10	1	-8/+7
\| \| \| \|	sub-packages
*	fixed nasty bug that made XGB not thread safe	Andrew Gallant (Ocelot)	2012-05-08	1	-1/+1
\|
*	use a custom logger so we don't stomp all over the global log configuration	Andrew Gallant (Ocelot)	2012-05-08	1	-17/+15
\|
*	gofmt	Andrew Gallant (Ocelot)	2012-05-07	1	-7/+7
\|
*	more clean up. use log instead of fmt.Print to stderr. bug fix for event ↵	Andrew Gallant (Ocelot)	2012-05-07	1	-46/+71
\| \| \| \|	blocking (a hack fix for now).
*	lots of docs and examples	Andrew Gallant (Ocelot)	2012-05-07	1	-6/+0
\|
*	80 cols	Andrew Gallant (Ocelot)	2012-05-07	1	-5/+6
\|
*	added tests	Andrew Gallant (Ocelot)	2012-05-07	1	-58/+40
\|
*	extensions are working! extensions are working!	Andrew Gallant (Ocelot)	2012-05-05	1	-23/+79
\|
*	oh momma. a lot of modifications and it appears to be working. w00t.	Andrew Gallant (Ocelot)	2012-05-05	1	-225/+233
\|
*	reworking xgb. cleaned up connection stuff a little. making new xid ↵	Andrew Gallant (Ocelot)	2012-05-03	1	-173/+86
\| \| \| \|	generation cleaner and use goroutines for it.
*	holy toldeo... things might actually be working	Andrew Gallant (Ocelot)	2012-05-03	1	-40/+32
\|
*	progress. still not working. this is incredibly difficult.	Andrew Gallant (Ocelot)	2012-04-29	1	-3/+19
\|
*	initial commit. not currently in a working state.	Andrew Gallant (Ocelot)	2012-04-28	1	-0/+484