Moved test files to test folder for organization.
Removed old wall methods from the board class and board tests.
Removed unimplemented code
added a getter to Game class
Working on making connections between server(s) & client

The Quoridor client will now take in CLA's and can parse them, it will be used
to make connections and store the socket information so the client can continue
to ask for moves, walls, booting, etc.. This will eventually start up a new
board and take care of all the players input.

I also modified the .gitignore file so that you don't have to worry about
adding files with a '~' at the end of them anymore. Also working on some tests.
More will be possible by using netcat.

The client should be mostly done (not starting a new game) by tommorow.
worked a little on the win state. not there yet
Added an interface to use for the Client/Server message passing scheme.

The client can now connect to sockets that are open and waiting for someone
to connect to them.

The interface (Messages.java) contains constant strings that will be used
between the Client/Server especcially when writing AI, and when making a
parser for the movement of pawns and placement of walls.
Implementing some of the client/server features necessary for starting a game

Following protocol for getting moves, getting names.
Progress on QuoridorServer.java
Trying to figure out implementation, will continue later

Trying to work the communication between server/client, will talk with
group to figure out how to start up listening for the socket so we
can start communicating back and forth.
I kept the Board.java class that was deleted because I'm not sure yet that it's obselete.

I'm reading up on a Subject/Observer design pattern that Ladd recommended when I asked him for
code design advice. I'll let everyone know what changes I propose today. If it turns out the Board
class is indeed obselete, I'll delete it. In one of my previous commits I did remove the old faulty
wall functionality.
Client can talk back and forth with a socket, loops forever requesting moves

Need to implement talking to the board, parsers, and logic checking for booting
players, verifying moves, etc. This will come with future additions and modularization.
Starting work on the parser/parsertest file

Parser will handle input from the move-servers in order to feed it
to and understand it by the client.
Wrote first test for parser to determine if the string passed in is a move

This can then be checked for logic problems/illegal moves.
Made parser pass one test

Had to move junit test for parser into package with source, it can be done in the seperate directory for tests but I couldn't figure it out quickly
win state is successfully implemented
forgot one thing