StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5065065
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-02-21T10:53:55.937
FavoriteCount
0
LastActivityDate
2011-02-21T10:53:55.937
LastEditDate
LastEditorUserId
0
OwnerUserId
105224
ParentId
5064844
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
A player is either <code>active</code> or <code>inactive</code>. Once he is active, he has to make a decision to <code>roll()</code> or to <code>hold()</code>. Each player has a strategy for this decision making process - a human player has the strategy in mind, the computer player needs a strategy implemented in code. This strategy could offer on method: <code>decide(int myScore, int oppenentsScorce)</code> and produce a result: to roll or not to roll. The <code>Player</code> class could look like this: <pre><code> public class Player { enum Decision { ROLL, HOLD } private Controller gameController; public Player(Controller gameController) { this.gameController = gameController; } // this is the real players strategy (-> Strategy pattern) abstract Decision decide(int myScore, int opponentsScore); // this method is called by the controller public void doTurn() { Decision decision = decide(gameController.getScore(this), gameControlle.getOpponentsScore(this); if (decision == ROLL) gameController.roll(this); if (decision == HOLD) gameController.hold(this); } } </code></pre> The <code>HumanPlayer</code> subclass could open a dialog for the human player, which shows the actual results and offers two buttons: roll / hold. The <code>ComputerPlayers</code> implementation would use an algorithm for the decision. The Controller controls the game, rolls the dice and keeps the score. And the controller checks after each turn, if there's a winner.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSeeking advice on Object-Oriented programming
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAndreas_D
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.