First playable version ready, please test for bugs.

[GoogleCodeExporter]

The first playable version has been completed.

Please take a look at GameFlowTest class to reproduce any specific game-flow.
All player actions should be possible.

Few critical featues that will be added soon (so please ignore while testing):
  * player with 0 chips is not removed from table (goes every time all-in
with 0 chips).
  * player who raises or bets with all his money is not automatically all-in.
  * player exit method needed to take care of consistency with dealer button. 

Original issue reported on code.google.com by kenzotom...@gmail.com on 14 Jul 2007 at 11:26

[GoogleCodeExporter]

Player who raises or bets with all his money is now automatically all-in. There 
was a
problem when a player tried to raise with a value higher than his stack but 
that's
solved now. There also was a double all-in message.

There is still a problem if a player wants to call a bet that's higher than his
stack. Then the pots must be split. I don't see anywhere where pots are split 
actually...

Added the BettingRulesTest class for testing the different betting rules. Still
working on that.

Original comment by cuypers....@gmail.com on 15 Jul 2007 at 2:19

[GoogleCodeExporter]

If a player calls a bet that is higher than his stack. He should invoke the 
all-in
method. All all-in players in a round are remembered and the pot is split at 
the end
of each round. It had to be implemented this way because several people can go 
all-in
in one round with different number of chips.

Original comment by kenzotom...@gmail.com on 15 Jul 2007 at 4:03

[GoogleCodeExporter]

Maybe it is better if we do not allow call,raise and bet with someone's whole 
stack
and throw an exception. A player should explicitly choose to go all-in. To 
prevent
going all-in by making a mistake for example (It's just my opinion, but it is
discutable.)

Original comment by kenzotom...@gmail.com on 15 Jul 2007 at 4:53

[GoogleCodeExporter]

Hmm, that's another way to do it of course :) I think it's best to re-use the
IllegalActionException for those cases. I'll implement it right away.

Original comment by cuypers....@gmail.com on 15 Jul 2007 at 6:15

[GoogleCodeExporter]

Original comment by guy...@gmail.com on 21 Jul 2007 at 4:33

• Changed state: Fixed