[Rails-devel] The Player Class

[<wak...@ea...>]

Over the last few days, I've been working on getting the initial game options working. If you check out the files in CVS and run the main() method in test/GameTest.java you'll see the current state of things.

However, it looks like the Player class needs some clean-up work done to it before I go too much further. 

Currently, there are methods that presume the Player is a collection for housing all players' data and there are methods that presume the Player is a singular object.

I think we need to pick one of these styles rather than cluttering up the class with the ability to work both ways.

In my opinion, it's very easy to use existing collections to store multiple singular Player objects (ex: Player[] allPlayers). This allows the Player class to focus on housing all the data specific to a single player and makes a bit more logical sense when we have Player extending CashHolder.


Thoughts?


---Brett.