StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7030275
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-11T17:30:37.967
FavoriteCount
0
LastActivityDate
2011-08-11T17:30:37.967
LastEditDate
LastEditorUserId
0
OwnerUserId
224988
ParentId
7030131
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
First of all, take a look at the default project structure. While it's not perfect, there are some default "Groups" in Xcode. Use those as a general guideline. (As you mentioned, Groups are not file system folders, although when you import resources you are prompted with the option to make groups for folders.) While there's not much official convention regarding the structuring of files, there are some things you can do, like I do, to scratch that organizational itch. I make a few subfolders in my project directory on my disk. Here are some of them: <ul> <li>Audio: Audio files also might get their own group.</li> <li>External Libraries: If I'm importing other people's code, I'll make a group called "libraries" and then a subgroup for each one. </li> <li>Images: In there, you can make subfolders/subgroups if you like. (One for icons, one for the main menu, etc.) </li> <li>Managed Objects: When I use Core Data in my projects, I'll often generate subclasses through Xcode's modeling tools. I like to keep those in a separate group and a seperate folder as well.</li> <li>View Controllers: Depending on the project, I might group my view controllers differently. For example, I might keep all of my "editors" and "viewers" in distinct groups.</li> </ul> Ultimately, Groups are for making your project management easier and Folders are for making file management easier. It's totally up to you how to do this. As Bill Brasky points out, at compile time, none of the organization really makes a difference. (If you want to go crazy, take a look at the "Build Phases" screen in Xcode 4. The copy phase is a jumble of all your relevant files.)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs there a "best practice" for Organization in Xcode 4?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMoshe
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
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.