StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4720250
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-01-18T03:37:36.097
FavoriteCount
0
LastActivityDate
2011-01-18T06:42:33.113
LastEditDate
2011-01-18T06:42:33.113
LastEditorUserId
125361
OwnerUserId
50294
ParentId
4719923
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<code>UITabBarController</code> kind of insists on grabbing the whole screen, so each tab will need to display its own instance of your title strip (At least, that's the path of least resistance. There are ways to force a single view to stay on top of all the tabs but they're more work.) Two basic approaches, one with a minor variation: <ul> <li><code>UITabBarController</code> contains n <code>UINavigationController</code>s, each of which contains one of your VCs as its root view controller. Each of these has a <code>UINavigationItem</code> with a custom title view containing your logo. Using a <code>UINavigationController</code> purely for its titlebar-ness is a totally apple-encouraged pattern; and if they ever need to, your VCs will be able to do navigation pushes easily.</li> <li><code>UITabBarController</code> contains your VCs directly; then (as mentioned in the comment above) each of those contains a <code>UIToolbar</code> somewhere in its own nib layout, probably across the top. Populate it however you like, probably with a <code>UIBarButtonItem</code> with a custom view, surrounded with flexible space items if you want it centered. Good/bad feature: your logo is actually a button if you do it this way.</li> <li>Same as 2, but with a <code>UINavigationBar</code> laid out similarly. <code>UINavigationBar</code>s can be used "naked" without a <code>UINavigationController</code>. Shouldn't need to subclass it, just stuff a navigationItem with a custom title view in there. This gives you centering and a textual title for free if you want 'em, and avoids the button behavior.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POStatic Title/Navigation Bar?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJonathan Sterling
UserOwnerUserId
1. USrgeorge
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POStatic Title/Navigation Bar?
 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.