The Project Window

Every software product starts out as a project. A project is the repository for all the elements used to design and build your product—including source files, user interface specifications, sounds, images, and links to supporting frameworks and libraries. The most visible type of software product you can create with Xcode is an application, but that’s not the only kind of project you can create. You can also develop Automator actions, command-line tools, frameworks, plug-ins, and kernel extensions.

The project window is the control center for an Xcode project. This section briefly describes each of the components in this window, except for the editing pane, which is described in Text Editor.

The Toolbar

The project window toolbar (identified in contains buttons and other controls you can use to perform common operations.

• The Overview pop-up menu lets you choose the active software development kit (SDK), configuration, target, executable, and architecture.

• The Action pop-up menu lists tasks you can perform on the currently selected item. You get the same menu when you Control-click an item.

• The Build and Run button compiles, links, and launches your application.

• The Breakpoints button turns on any breakpoints that you’ve set and changes the Build and Run button to Build and Debug.

• The Tasks button allows you to stop any operation in progress.

• The Info button opens a window that displays information and settings for groups, files, and targets in your project. You can change many settings in an Info window.

• The search text field filters the items currently displayed in the detail view.

You can customize what’s available on the toolbar.

Text Editor

In addition to displaying content that you can edit, the text editor provides a navigation bar at the top, and a gutter and focus ribbon to the left of the content. You can view and edit a source file within the project window by selecting the file in the Groups & Files list. If you prefer to view and edit a source file in its own window, double-click the file in the Groups & Files list.

The gutter displays line numbers, as well as information about the location of breakpoints, errors, or warnings in the file.

The focus ribbon, as its name suggests, helps you to concentrate your attention on parts of your code by:

• Identifying the scope of a block of code

• Allowing you to hide and show blocks of code

The bar along the top of the editor contains several menus and buttons that let you move between files you’ve viewed, jump to symbols, and switch to other open files.

Although you can hold the pointer over each item to see a tooltip that provides a description of each item, these items need more explanation:

• The function menu shows the function and method definitions in the current file. When you choose a definition from this menu, the editor scrolls to the location of that definition. The menu lets you jump to many points in the current file, including any identifier declared or defined in the file. You can also add items that aren’t definitions or declarations.

• The class hierarchy menu is especially useful if you are new to Objective-C. You can quickly access the header files of the superclasses of any class in your application, which lets you investigate inherited methods and properties.

• The included files menu lists files included by the current file as well as the files that include the current file. Choosing a file from this menu opens that file in the editor.

• The Counterpart button opens the counterpart of the current file or jumps to the symbolic counterpart of the currently selected symbol.

  Clicking the Counterpart button opens the related header or source file for the file currently open in the text editor. For example, if the file currently open in the editor is MyFile.c, clicking this button opens MyFile.h, and vice versa.

  Option-clicking the Counterpart button displays the counterpart of the currently selected symbol—class, method, function, and so on—opening the corresponding file and scrolling to the appropriate section within it if necessary. If the selected symbol is a class, method, or function declaration, the editor scrolls to the definition for that item. If a class, function, or method definition is currently selected, the editor scrolls to the symbol’s declaration.

Two other text editor important features—code completion and Quick Help—are described next.

The Documentation Window

You can use the Documentation window to search through all developer documentation (API reference, guides, sample code, technical notes, release notes, and technical Q&A documents). As you enter a term in the search field, Xcode simultaneously performs API reference, document title, and full text searches.

Targets and Build Phases

A target contains the instructions for building a finished product from a set of files in a project—for example, a framework, library, application, or command-line tool. A simple Xcode project has just one target that produces one product. A larger development effort with multiple products may require a more complex project containing several related targets. For example, a project for a client-server software package may contain targets that create a client application, a server application, command-line tool versions of the client and server functionality, and a private framework that all the other targets use.

Build phases are instructions that Xcode follows to build a target. Each build phase consists of a list of input files and a task to be performed on each of those files. Common build phases include compiling files, linking object files, and copying resource files.

The CFLocalServer project has three targets. One builds a server program, one builds a client application, and another is a target whose purpose is to sequentially build the other targets. You can customize how a project is built by adding phases. To add a phase, choose Project > New Build Phases.

Build Settings

A build setting is a variable that contains information used to build a product. For each operation performed in the build process—such as compiling Objective-C source files—build settings control how that operation is performed. For example, the information in a build setting specifies the options Xcode passes to the tool—in this case, the compiler.

Each target can specify one or more sets of build settings, called build configurations. Targets are preconfigured with two build configurations, debug and release. The debug build configuration specifies build settings that generate products containing information that is useful during development, such as debug symbols. The release build configuration specifies build settings appropriate for products that are ready to deploy to your customers.

Build Products

By default, Xcode places the built application bundle inside your project’s build folder. You can run a built application from the Finder by double-clicking the application icon located in Debug or Release folder in your project’s build folder. Which folder depends on whether the active build configuration is debug or release.

Preferences and Keyboard Shortcuts

Xcode preferences let you customize just about everything in the development environment including the behavior of the text editor, where build products are stored, code colors and indentation, code repositories, and the content shown in Quick Help.

One popular set of preferences is Key Bindings, which lets you change the keyboard shortcuts for actions accessible through menu items or the keyboard, such as paging through a document or moving the cursor. You can choose a predefined set of keyboard shortcuts for menu items and other tasks, or you can create your own set. The predefined sets include sets that mimic BBEdit, Metrowerks, and MPW.