StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12912014
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-16T09:56:03.207
FavoriteCount
0
LastActivityDate
2012-10-16T10:02:29.427
LastEditDate
2012-10-16T10:02:29.427
LastEditorUserId
671858
OwnerUserId
671858
ParentId
12911852
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The difference between a view and its controller can be properly framed in the context of the <a href="http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller" rel="nofollow">Model-View-Controller pattern</a> (also have a look at <a href="http://www.codinghorror.com/blog/2008/05/understanding-model-view-controller.html" rel="nofollow">this post</a>): <blockquote> A view is a (visual) representation of its model. It would ordinarily highlight certain attributes of the model and suppress others. It is thus acting as a presentation filter. A view is attached to its model (or model part) and gets the data necessary for the presentation from the model by asking questions. It may also update the model by sending appropriate messages. All these questions and messages have to be in the terminology of the model, the view will therefore have to know the semantics of the attributes of the model it represents. A controller is the link between a user and the system. It provides the user with input by arranging for relevant views to present themselves in appropriate places on the screen. It provides means for user output by presenting the user with menus or other means of giving commands and data. The controller receives such user output, translates it into the appropriate messages and pass these messages on to one or more of the views. </blockquote> The idea is that the view is responsible for the visual representation of the data contained in the model; the controller is responsible for the user interaction and communication between the view and the model, roughly speaking. This applies to the relationship between <code>UIView</code> and <code>UIViewController</code>, as well as to the relationship between <code>UITableView</code> and <code>UITableViewController</code>, etc. Also to be noted that while <code>UIView</code>/<code>UIViewController</code> has no provision for a model class (since they are very broad classes, so the model could be anything), <code>UITableView</code>/<code>UITableViewController</code> do define a model in the form of the table data source and it <code>UITableViewDataSource</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat's the difference between a UIClass and UIClassController?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsergio
UserOwnerUserId
1. USsergio
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
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.