StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15280510
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-03-07T19:55:38.067
FavoriteCount
0
LastActivityDate
2013-03-12T22:04:37.843
LastEditDate
2013-03-12T22:04:37.843
LastEditorUserId
1973271
OwnerUserId
51292
ParentId
15026549
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<p>This is just an idea, but consider if the mediator pattern is applicable.</p> <p>From <a href="http://en.wikipedia.org/wiki/Design_Patterns" rel="nofollow">the gang of four</a>:</p> <blockquote> <h2>Intent</h2> <p>Define an object that encapsulates how a set of objects interact. Mediator promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.</p> <h2>Applicability</h2> <p>Use the Mediator pattern when</p> <ol> <li>a set of objects communicate in well-defined but complex ways. The resulting interdependencies are unstructured and difficult to understand.</li> <li>reusing an object is difficult because it refers to and communicates with many other objects.</li> <li>a behavior that's distributed between several classes should be customizable without a lot of subclassing.</li> </ol> <h2>Consequences</h2> <p>The Mediator pattern has the following benefits and drawbacks:</p> <ul> <li>It limits subclassing. A mediator localizes behavior that otherwise would be distributed among several objects. Changing this behavior requires subclassing Mediator only; Colleague classes can be reused as is.</li> <li>It decouples colleagues. A mediator promotes loose coupling between colleagues. You can vary and reuse Colleague and Mediator classes independently.</li> <li>It simplifies object protocols. A mediator replaces many-to-many interactions with one-to-many interactions between the mediator and its colleagues. One-to-many relationships are easier to understand, maintain, and extend.</li> <li>It abstracts how objects cooperate. Making mediation an independent concept and encapsulating it in an object lets you focus on how objects interact apart from their individual behavior. That can help clarify how objects interact in a system.</li> <li>It centralizes control. The Mediator pattern trades complexity of interaction for complexity in the mediator. Because a mediator encapsulates protocols, it can become more complex than any individual colleague. This can make the mediator itself a monolith that's hard to maintain.</li> </ul> </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONested MVC communication patterns
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USflup
UserOwnerUserId
1. USRay Tayek
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
  VTApproveEditSuggestion
CommentsPostId
1. COThanks for the reply. I'm not quite sure how wire up a mediator for the scenario I described though :(
  singulars
  PostPostId
  PO
  UserUserId
  USchinabuffet
2. COme neither, i just thought it would ring a bell. the gof book say: "MVC supports nested views with the CompositeView class, a subclass of View. CompositeView objects act just like View objects; a composite view can be used wherever a view can be used, but it also contains and manages nested views.", so maybe http://stackoverflow.com/questions/13578312/mvc-difference-between-two-step-and-composite-view-patterns or http://c2.com/cgi/wiki?ModelViewControllerAsAnAggregateDesignPattern would give you some ideas.
  singulars
  PostPostId
  PO
  UserUserId
  USRay Tayek

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.