StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6620356
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-07-08T05:39:59.837
FavoriteCount
0
LastActivityDate
2011-07-08T05:39:59.837
LastEditDate
LastEditorUserId
0
OwnerUserId
622725
ParentId
3776197
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
As I understand your requirement, you want a split view controller as the main controller. The left panel will select an item and the right detail view for that item will contain 3 tabs. Each tab will have a navigation controller. The app store follows a pattern similar to the detail view. Its important to structure your controllers as a tree. <ul> <li>root: split view controller <ul> <li>list view: table controller (MasterViewController for selecting fruit)</li> <li>detail view: tab controller (all info about watermelon) <ul> <li>tab1: navigation controller <ul> <li>page 1: first tab root controller (history of watermelons)</li> </ul></li> <li>tab2: navigation controller <ul> <li>page 1: first tab root controller (map of watermelon farms)</li> </ul></li> <li>tab3: navigation controller <ul> <li>page3: first tab root controller (watermelon recipes)</li> </ul></li> </ul></li> </ul></li> </ul> With this pattern you can create the controller structure on viewDidLoad, but then change the contents of page 1, 2, 3 when responding to setDetailItem UINavigatorContoller has a popToRootViewControllerAnimated message that can reset the previous navigation controller stack for each of the 3 navigation controllers. When I started learning ios development, I found setting up the controller hierarchies in code easier than using interface builder. IB is faster once you get the concepts. You can still create an IB nib controller for page1,2,3 root view controllers. good reference: <a href="http://developer.apple.com/library/ios/#featuredarticles/ViewControllerPGforiPhoneOS/Introduction/Introduction.html#//apple_ref/doc/uid/TP40007457" rel="nofollow">http://developer.apple.com/library/ios/#featuredarticles/ViewControllerPGforiPhoneOS/Introduction/Introduction.html#//apple_ref/doc/uid/TP40007457</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAdd navigationcontroller to detail view in splitview
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USgreg
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
2. 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.