Comments on: Code Organization in Xcode Projects

By: AlexH

AlexH — Wed, 23 Jun 2010 12:02:51 +0000

Further to my last comment: the failure point of declaring @property in the (Private) category is actually at the point of @synthesize, not the @property declaration itself.

By: AlexH

AlexH — Wed, 23 Jun 2010 11:59:19 +0000

On the subject of using categories for private methods: I use this myself, but I prefer to use the empty category, i.e. “ClassName ()”, and not “ClassName (Private)”. Apple refer to the empty category as “Extension” and it actually behaves differently: you can declare @property items inside the empty category (and hence have private getters and setters). A category called ‘Private’ won’t allow that.

By: iPhoneConnection

iPhoneConnection — Tue, 11 May 2010 22:29:28 +0000

Great article. A very insightful way of structuring an XCode project.

By: Adrian Kosmaczewski

Adrian Kosmaczewski — Mon, 04 Jan 2010 07:15:12 +0000

Thanks Ben! Happy new year!

By: Ben

Ben — Sun, 03 Jan 2010 20:29:32 +0000

Great article. Being used to developing in TextMate (and wanting to continue using it’s snippets for Objective-C), I was perplexed as how to organize the code outside of Xcode. Very helpful.

By: Adrian

Adrian — Mon, 17 Aug 2009 17:02:02 +0000

@Rudi Of course! Excellent idea. Thanks for sharing!

By: Rudi Farkas

Rudi Farkas — Sat, 15 Aug 2009 16:19:49 +0000

Good advice, will be followed.

On the related subject of sharing source files across many projects, I have a directory structure similar to : iphoneprojects shared logging dlog.h dlog.m nsstringext ... opengltools .... whatevertools firstiphoneproj secondiphoneproj otheriphoneproj

I add shared files, without copying them, to projects that need them.

Seems fairly obvious, but I haven't seen discussions on this subject. Do you have any comments or recommendations ?

Rudi

By: Nicolas Seriot

Nicolas Seriot — Tue, 28 Jul 2009 23:01:45 +0000

Nice wrap-up! But in the project layout as seen in the Finder (second screenshot) I can see a build folder...

You can put build folders in a customized location in Xcode Preferences > Building > Place Build Products in > Customized Location, say /Library/XcodeBuilds/.

This way, build folders do not clutter the projects folders anymore. You don't have to add them to the SCM system ignore list, you spare time and place when you zip a project, and you can easily avoid backuping build folders by adding a single folder into Time Machine black list.