Databases
StackOverflow2013
Postsdbo
POWhat is the best way to organize source code of a large Cocoa application in Xcode?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat is the best way to organize source code of a large Cocoa application in Xcode?
    primarykey
    data
    text
    <p>Here is what I'm looking for: </p> <p>I'd like to separate pieces of functionality into modules or components of some sort to <em>limit visibility of other classes to prevent that each class has access to every other class</em> which over time results in spaghetti code.</p> <p>In Java &amp; Eclipse, for example, I would use packages and put each package into a separate project with a clearly defined dependency structure.</p> <p>Things I have considered:</p> <ol> <li>Using <strong>separate folders</strong> for source files <strong>and using Groups in Xcode</strong>: <ul> <li>Pros: simple to do, almost no Xcode configuration needed</li> <li>Cons: no compile-time separation of functionality, i.e. access to everything is only one <code>#import</code> statement away</li> </ul></li> <li><strong>Using Frameworks</strong>: <ul> <li>Pros: Framework code cannot access access classes outside of framework. This enforces encapsulation and keeps things separate</li> <li>Cons: Code management is cumbersome if you work on multiple Frameworks at the same time. Each Framework is a separate Xcode project with a separate window</li> </ul></li> <li><strong>Using Plugins</strong>: <ul> <li>Pros: Similar to Frameworks, Plugin code can't access code of other plugins. Clean separation at compile-time. Plugin source can be part of the same Xcode project.</li> <li>Cons: Not sure. This may be the way to go...</li> </ul></li> </ol> <p>Based on your experience, what would you choose to keep things separate while being able to edit all sources in the same project?</p> <p><strong>Edit:</strong></p> <ul> <li>I'm targeting Mac OS X</li> <li>I'm really looking for a solution to enforce separation at compile time</li> <li>By plugins I mean Cocoa bundles (http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/LoadingCode/Concepts/Plugins.html)</li> </ul>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMark
    1. USMark
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhat is the best way to organize source code of a large Cocoa application in Xcode?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhat is the best way to organize source code of a large Cocoa application in Xcode?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhat is the best way to organize source code of a large Cocoa application in Xcode?
      1. USJano
      1. VTFavorite
    1. COMajor con to plugins: they're not valid under iOS. Hope you're targeting OS X. Under Xcode 4 managing multiple targets and projects in the same window - Frameworks included - is pretty easy, you just need to go File > New Workspace.
      singulars
      1. POWhat is the best way to organize source code of a large Cocoa application in Xcode?
      1. USMorgan Harris
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload