Sending messages properly back and forth using the new driver architecture, and a proper message queue+program completion

Work on splitting up the driver into multiple files (we can ignore the .pyc files this produces)

Reorg

Start jobs on the driver side

exporter.py as more of a driver program, doing all file IO. Exporter.fla as the new flash component

Force all _trace's to be _strace's. Also, wasn't passing GraphicDefs around properly (no GameData/GraphicFactory!)

Export jobs are queued, but they aren't getting to the exporter... (where is our log going?)

Start passing jobs

Bidirectional command passing

Sending commands either via cmd line or stdin (also update .gitignore to ignore *.airi files, since it's easier to just produce those instead of signing an exe if we are using the projector version)

Reading all args for now

Hand roll the parsing so we can parse stdin for commands if we get "-" passed as input

Start rolling our own args parsing so we can do it the way I want :(

More playing with arg parsing

Better command handling and arg parsing from the wrapper

Ignore the GraphicExport.app (not using it for now) and certificate

Start a wrapper program, "./exporter.py" which creates a simple socket server, and then starts GraphicExport.exe, which now attempts to find that server in order to accept commands and do console IO. ...

Should work with either the air-runtime-bundled app, or the projector exe.
I only included the projector exe as the air runtime one is a little more heavy-weight.
The downside to the projector exe is that it can't accept cmd line arguments, so we just have to hope that we pick the right default port that exporter.py is using (7890 currently)

Bare exporter to produce json/png files from swfs