StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3577786
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-08-26T17:34:32.013
FavoriteCount
0
LastActivityDate
2010-08-26T17:39:38.787
LastEditDate
2010-08-26T17:39:38.787
LastEditorUserId
40516
OwnerUserId
40516
ParentId
3577626
PostTypeId
2
Score
15
ViewCount
0
LastEditorDisplayName
text
Body
In general, rules of thumbs are exactly that: rules of thumb. Not immutable laws that one should never deviate from -- I'm pretty sure you'll find cases where doing things with your dependencies in your constructor makes more sense than otherwise. With that in mind, let's revisit your particular design: <blockquote> So this FallingPiece class has the responsability of controlling the current falling piece in a tetris game. When the piece hits the bottom or some other place, raises an event signaling that and then, through the factory, generates another new piece that starts falling again from above. </blockquote> Seems weird to me that <code>FallingPiece</code> triggers the piece generator after its finished. I'd design it something like this: <pre><code>class PieceGenerator { public FallingPiece NextFallingPiece() { FallingPiece piece = new FallingPiece(NextPiece()); return piece; } // ... } class GameEngine { public PieceGenerator pieceGenerator = new PieceGenerator(); public void Start() { CreateFallingPiece(); } void CreateFallingPiece() { FallingPiece piece = pieceGenerator.NextFallingPiece(); piece.OnStop += piece_OnStop; piece.StartFalling(); } void piece_OnStop(FallingPiece piece) { piece.OnStop -= piece_OnStop; if (!GameOver()) CreateFallingPiece(); } } </code></pre> At least with this design, the <code>GameEngine</code> is fully responsible for telling the Generator when to create its pieces, which seems more idiomatic than the FallingPiece having that duty.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PO"Classes should never perform work involving Dependencies in their constructors."
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJuliet
UserOwnerUserId
1. USJuliet
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PO"Classes should never perform work involving Dependencies in their constructors."
 singulars
 PostTypePostTypeId
 PTQuestion
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.