StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8208890
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-21T08:08:19.577
FavoriteCount
0
LastActivityDate
2011-11-21T08:08:19.577
LastEditDate
LastEditorUserId
0
OwnerUserId
731115
ParentId
8196855
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
1) Controller responsibility is primarily "execute an action, choose an appropriate view, provide some data to that view and return the view to a user". 2) As MVC tries to separate presentation logic and UI rendering, I believe, controller shouldn't attempt to perform any of view responsibilities: listening to UI events or pre-formatting of values <code>dateString = data.ToString('YYYY-MM')</code> - that's all should go to view. 3) in MVC view knows all about a model - model is rendered by view without any controller involvement (that's primary 'issue' fixed by MVP, where view should and model should unbound as much as possible). However it's not recommended for view to query model directly. Instead, all data changes should be reported to view by model using Observer pattern. Consider the following - <a href="http://upload.wikimedia.org/wikipedia/commons/b/b5/ModelViewControllerDiagram2.svg" rel="nofollow">schema from wikipedia article</a> - dashed line from model to view indicates that fact. Just keep in mind that model is more viewmodel here and shouldn't really be a part of BL layer. So here scenario could be the following: <ul> <li>User clicks "add item"</li> <li>View sends request to the controller with the item data</li> <li>Controller makes call to BL, which makes changes to the model (adds new item to the list).</li> <li>Model fires "updated" event to the view (or "error" event, if there are some issues in underlying layers)</li> <li>View updates UI according to changes reported.</li> </ul> 4) The statement is perfectly true. In MVC you shouldn't do that. I assume, in MVP you shouldn't do that as well - I mean, listening to events from UI directly. That should be done either by forwarding event by view; or using a platform-independent view representation, like <pre><code>inderface IMyGridView { event ItemEvent AddItemClick; } </code></pre> (which doesn't make sense for MVC, as view is pretty much independent from a controller and mostly all view actions are result in calls to controller).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat all things can be stuffed inside a controller in MVC?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmikalai
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. This table or related slice is empty.
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.