Start shifting over to the framework that play-clj uses.

Namely, splitting the application/window-specific pieces
away from the actual graphics portions
Refactor events into their own namespace

Refactor is probably too grand a word. Did a big cut and
paste to try to trim back on my distractions. Apparently none of them
are actually getting used/referenced at the moment. I'm pretty sure
there's still some sort of value to be found in what is there.
Cleaned up basic syntax error silliness.

Got it back to the point where my unit tests fail due to 0mq socket
state issues.
Track down issues w/ starting Components.

The main problem stemmed from Components that were returning nil and
documentation/error messages that didn't make it blatantly obvious that
this is actually a major problem.

Up to the point of failing because the things I was doing in my
background threads don't mesh well with the way I'm trying to do those
same things (or not) now.
Really just beating my head against build errors

A lot of what's here was trying to break things into smaller pieces so I
could cope with compiler errors and try to split the ball of mud into at
least slightly more manageable pieces.

Wound up spending almost all evening fighting with java imports.
I think I may have hit on the magical combination.

The ns declaration seems to fail unless the import happens after the ns
involved in the import has already been required. It also seems as
though that ns needs to do a gen-class so its output can be seen.

I could still be totally out in left field, but I think those changes
are what got me past some basic linking errors. Which is a truly
uncomfortable state of affairs.
Get it to build again
Work on being able to run (refresh).

Wind up with component exceptions when I actually try to start the
system.

Have things back around to my broken background communication thread.
Just realized that I'm not seeing error logs.

Most of the other log levels show up in the REPL. Errors
aren't. Apparently I can't just provide a relative path to the log file
and hope it shows up somewhere on the CLASSPATH (although I suppose it
might be hidden in there somewhere).
Figured out the 'background communications thread'

It's more of a "track heartbeat from client" thread really.

Tie it in as a middleman between the FSM and the socket that's coupled
from the client. Now it seems redundant.
Get past Application start part of Lifecycle.

Still can't get REPL working because of broken unit test, but this is
a *huge* step forward.
Start trying to clean up broken unit test.

There seems to be only one of them so far, probably because I don't have
any sort of meaningful/useful test coverage.

This version fails on the initial (reset). Then it draws an unresponsive
window when I call (refresh). The REPL keeps interacting, though I don't
see anything but a blank black screen.

Still, that's another step forward, isn't it?