StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7791328
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-17T08:44:51.287
FavoriteCount
0
LastActivityDate
2011-10-17T08:44:51.287
LastEditDate
LastEditorUserId
0
OwnerUserId
412916
ParentId
7497283
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The quote is at Introduction > Style: <blockquote> We will always create view controllers programmatically. Some programmers will instantiate view controllers inside XIB file. We've found this practice leads to projects that are difficult to comprehend and debug. </blockquote> They talk about instantiation. If you have two view controllers A,B, you can alloc/init B in A's implementation, or you can drop a reference to B in A's XIB. In both cases, B may be defined in a XIB or not (the Big Ranch book advises to use XIBs for complex view controllers btw). <hr> Anyway, here is the difference: <pre><code>CitySelectionVC *citySel = [[[CitySelectionVC alloc] initWithCities:self.cities] autorelease]; [self.navigationController pushViewController:citySel animated:TRUE]; </code></pre> vs <pre><code>citySel.cities = self.cities; [self.navigationController pushViewController:citySel animated:TRUE]; </code></pre> First case is a explicit instantiation in code. It tells me: <ul> <li>The VC is created now.</li> <li>It needs the cities to work.</li> </ul> The code in the second block references an outlet instantiated in the XIB. It tells me: <ul> <li>A VC was instantiated at unknown time, with unknown requirements.</li> <li>I'm passing the cities.</li> </ul> I favor the first style because it is more explicit, and gives me control of the lifespan of the object. In iOS 5 you can use Storyboards to create transitions and pass information between controllers. See Session 309 of WWDC2011.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow does instantiating view controllers inside Xib files lead to code that is difficult to comprehend and debug?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJano
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow does instantiating view controllers inside Xib files lead to code that is difficult to comprehend and debug?
 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
 VTBountyClose
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.