# Plan meeting.

API.'
(3 minimum api he gave us to start)
Player, Engine, Data
'
First Sprint.
- Draw, Stud and Shared
- Draw: players receive cards face-down at the start of each round. Each round, "surviving" players can discard cards from their hand and receive replacements from the dealer.
- Stud: players receive some cards face-up and some cards face-down.
- Shared (aka Texas Hold'em): players receive some cards individually and there's also a community pool of cards.

Shared functionality:
- Betting:
- Each round, there is an "ante" in the pot. The first player can "call" or "raise"
- If any player raises, all following players must either call the upped ante, raise the upped ante more, or fold
- Once everyone has either called or folded, betting is over for that round. Anyone who has not folded "survives" into the next round
- Winning hands:
- Can be read in as a data file
- How to end the game:
- If everyone but one person folds

Different functionality:
- Whether cards are face-up or face-down:
- In Draw, all players' cards are face-down at all times.
- In Stud, some players' cards are face-up and some are face-down (in 5 Card Stud, every player only gets one face-down card, called the "hole" card)
- In Shared, players' individual cards are face-down. There is a community pool that is face-up.
- Starting hand:
- In Draw, players start with 5 cards
- In Stud, players start with 1 card face-down and 1 card face-up
- In Shared, players start with 2 cards
- What happens after each betting round:
- In Draw, players are allowed to discard 0-3 cards and draw an equal number of replacements. This happens one player at a time.
- In Stud, players are dealt an additional card face-up
- In Shared, after the first round three cards are placed in the community pool. Next, another card is added to the pool. Finally, one card is added to the pool (max 5 in the pool)

## Distribution of Work.
- 2 people on Data
- Rachel, Livia
- 1 person on Engine
- Patrick
- 1 person on view/player
- Martha
- Montana can also help with this.
- 1 person on Controller/Connecting all the API's.
- Montana

Data API.
- XML

## Game flow.
- Starts with player api
+ pick game from view

### Player Api.

- Send User game choice to Data.
- There would already be an existing
data file for the basic non customizabale rules of that game.
- Interact with data writer interface to write user preferences into xml file of some structure to be determined later.

### Data Api.
- Data after reading the file uses reflection to initialize the data object.
- Send the user choice for game to engine in a meaningful way.
- Create Card classes
- Create Deck class.
- 2 basic interfaces. Reading and writing from the data files.
-