From: Sam Moore <matches@ucc.asn.au>
Date: Wed, 30 Jan 2013 13:00:50 +0000 (+0800)
Subject: It works!
X-Git-Url: https://git.ucc.asn.au/?p=progcomp2013.git;a=commitdiff_plain;h=a238aa7acac990bae67644d1dc7f518ce3e2e8c6;hp=a238aa7acac990bae67644d1dc7f518ce3e2e8c6

It works!

Need to tidy things up. Differ between 'short' log and full log. Make HttpGetter work for either.

"short" log has the entire board state and most recent selection/move.
"full" log has the original board state and all moves up to the current point.

I started the "short" log so I could make it easy to watch games played on the server, but I think it might be useful
for testing now. But I need to work on it first.

Since short log prints the board state rather than all moves, agents don't know what is going on when short log is read back.
If I implement an API for that, then people can write their own starting game states.

Also need to indicate whether pieces are revealed or not in their string, and interpret correctly in reading the short logs

Or not...
perhaps this is getting too complicated?

NEVER
---