StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6946485
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-04T18:14:52.500
FavoriteCount
0
LastActivityDate
2011-08-04T19:34:05.970
LastEditDate
2011-08-04T19:34:05.970
LastEditorUserId
428767
OwnerUserId
428767
ParentId
6945840
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
In cases where UISplitViewController won't cut it or you can't use it because you're on the iPhone, there are a number of different ways to do this: <ol> <li>Create a parentController that alloc/inits two child viewControllers and then adds their views as subviews. This is the approach I use when I need to, but I should warn that Apple advises against it in the <a href="http://developer.apple.com/library/ios/#featuredarticles/ViewControllerPGforiPhoneOS/AboutViewControllers/AboutViewControllers.html#//apple_ref/doc/uid/TP40007457-CH112-SW12" rel="nofollow">Note section of the View Controller Programming Guide</a></li> <li>Create a parentController that is responsible for say the left side but it alloc/inits a child viewController that is responsible for the right side and adds its view as a subview. Same caveat as above, Apple advises against it.</li> <li>Similar to the above, but use the Apple recommended approach of having your sub controllers subclass NSObject instead of UIViewController. Here's <a href="http://blog.carbonfive.com/2011/03/09/abusing-uiviewcontrollers/" rel="nofollow">a good blog post on the subject</a>.</li> <li>Jam it all together into one monster viewController that is responsible for everything. This is the most common approach you'll find used if you're inheriting old iOS code (and in my opinion the worst).</li> </ol> I personally prefer the first, second, or third approaches as it leads to better separation of concerns, good encapsulation, and therefor cleaner and easier to maintain code. I also find that later on if we change the flows to move away from a split style view to two different screens, the individual viewControllers are completely re-usable because they are well encapsulated.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSplitting a view into two
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USToddH
UserOwnerUserId
1. USToddH
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSplitting a view into two
 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
 VTAcceptedByOriginator
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.