<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Code Organization in Xcode Projects</title>
	<atom:link href="http://akosma.com/2009/07/28/code-organization-in-xcode-projects/feed/" rel="self" type="application/rss+xml" />
	<link>http://akosma.com/2009/07/28/code-organization-in-xcode-projects/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=code-organization-in-xcode-projects</link>
	<description>Leading international provider of cross-platform and multilingual software solutions, for iPhone, iPad, Mac, Windows, Linux, Android, and the web.</description>
	<lastBuildDate>Tue, 07 Sep 2010 05:11:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: AlexH</title>
		<link>http://akosma.com/2009/07/28/code-organization-in-xcode-projects/comment-page-1/#comment-802</link>
		<dc:creator>AlexH</dc:creator>
		<pubDate>Wed, 23 Jun 2010 12:02:51 +0000</pubDate>
		<guid isPermaLink="false">http://kosmaczewski.net/?p=1710#comment-802</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlexH</title>
		<link>http://akosma.com/2009/07/28/code-organization-in-xcode-projects/comment-page-1/#comment-801</link>
		<dc:creator>AlexH</dc:creator>
		<pubDate>Wed, 23 Jun 2010 11:59:19 +0000</pubDate>
		<guid isPermaLink="false">http://kosmaczewski.net/?p=1710#comment-801</guid>
		<description>On the subject of using categories for private methods: I use this myself, but I prefer to use the empty category, i.e. &quot;ClassName ()&quot;, and not &quot;ClassName (Private)&quot;. Apple refer to the empty category as &quot;Extension&quot; and it actually behaves differently: you can declare @property items inside the empty category (and hence have private getters and setters). A category called &#039;Private&#039; won&#039;t allow that.</description>
		<content:encoded><![CDATA[<p>On the subject of using categories for private methods: I use this myself, but I prefer to use the empty category, i.e. &#8220;ClassName ()&#8221;, and not &#8220;ClassName (Private)&#8221;. Apple refer to the empty category as &#8220;Extension&#8221; and it actually behaves differently: you can declare @property items inside the empty category (and hence have private getters and setters). A category called &#8216;Private&#8217; won&#8217;t allow that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iPhoneConnection</title>
		<link>http://akosma.com/2009/07/28/code-organization-in-xcode-projects/comment-page-1/#comment-613</link>
		<dc:creator>iPhoneConnection</dc:creator>
		<pubDate>Tue, 11 May 2010 22:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://kosmaczewski.net/?p=1710#comment-613</guid>
		<description>Great article.  A very insightful way of structuring an XCode project.</description>
		<content:encoded><![CDATA[<p>Great article.  A very insightful way of structuring an XCode project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Kosmaczewski</title>
		<link>http://akosma.com/2009/07/28/code-organization-in-xcode-projects/comment-page-1/#comment-214</link>
		<dc:creator>Adrian Kosmaczewski</dc:creator>
		<pubDate>Mon, 04 Jan 2010 07:15:12 +0000</pubDate>
		<guid isPermaLink="false">http://kosmaczewski.net/?p=1710#comment-214</guid>
		<description>Thanks Ben! Happy new year!</description>
		<content:encoded><![CDATA[<p>Thanks Ben! Happy new year!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://akosma.com/2009/07/28/code-organization-in-xcode-projects/comment-page-1/#comment-213</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Sun, 03 Jan 2010 20:29:32 +0000</pubDate>
		<guid isPermaLink="false">http://kosmaczewski.net/?p=1710#comment-213</guid>
		<description>Great article. Being used to developing in TextMate (and wanting to continue using it&#039;s snippets for Objective-C), I was perplexed as how to organize the code outside of Xcode. Very helpful.</description>
		<content:encoded><![CDATA[<p>Great article. Being used to developing in TextMate (and wanting to continue using it&#8217;s snippets for Objective-C), I was perplexed as how to organize the code outside of Xcode. Very helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://akosma.com/2009/07/28/code-organization-in-xcode-projects/comment-page-1/#comment-82</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Mon, 17 Aug 2009 17:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://kosmaczewski.net/?p=1710#comment-82</guid>
		<description>@Rudi
Of course! Excellent idea. Thanks for sharing!</description>
		<content:encoded><![CDATA[<p>@Rudi<br />
Of course! Excellent idea. Thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rudi Farkas</title>
		<link>http://akosma.com/2009/07/28/code-organization-in-xcode-projects/comment-page-1/#comment-81</link>
		<dc:creator>Rudi Farkas</dc:creator>
		<pubDate>Sat, 15 Aug 2009 16:19:49 +0000</pubDate>
		<guid isPermaLink="false">http://kosmaczewski.net/?p=1710#comment-81</guid>
		<description>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&#039;t seen discussions on this subject.
Do you have any comments or recommendations ?

Rudi</description>
		<content:encoded><![CDATA[<p>Good advice, will be followed.</p>
<p>On the related subject of sharing source files across many projects, I have a directory structure similar to :<br />
iphoneprojects<br />
   shared<br />
      logging<br />
         dlog.h<br />
         dlog.m<br />
     nsstringext<br />
       &#8230;<br />
     opengltools<br />
        &#8230;.<br />
     whatevertools<br />
  firstiphoneproj<br />
  secondiphoneproj<br />
  otheriphoneproj</p>
<p>I add shared files, without copying them, to projects that need them.</p>
<p>Seems fairly obvious, but I haven&#8217;t seen discussions on this subject.<br />
Do you have any comments or recommendations ?</p>
<p>Rudi</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas Seriot</title>
		<link>http://akosma.com/2009/07/28/code-organization-in-xcode-projects/comment-page-1/#comment-80</link>
		<dc:creator>Nicolas Seriot</dc:creator>
		<pubDate>Tue, 28 Jul 2009 23:01:45 +0000</pubDate>
		<guid isPermaLink="false">http://kosmaczewski.net/?p=1710#comment-80</guid>
		<description>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 &gt; Building &gt; Place Build Products in &gt; Customized Location, say /Library/XcodeBuilds/.

This way, build folders do not clutter the projects folders anymore. You don&#039;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.</description>
		<content:encoded><![CDATA[<p>Nice wrap-up! But in the project layout as seen in the Finder (second screenshot) I can see a build folder&#8230;</p>
<p>You can put build folders in a customized location in Xcode Preferences &gt; Building &gt; Place Build Products in &gt; Customized Location, say /Library/XcodeBuilds/.</p>
<p>This way, build folders do not clutter the projects folders anymore. You don&#8217;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.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
