Information Technology Reference
In-Depth Information
Adding miscellaneous other files from the templates
The templates include a selection of other files. You can add them to a project in the usual ways.
The C/C++ templates add a standard C or C++ pair of header and code files. You can import these into
Objective-C code in the usual way. For more about working with these languages, see Chapter 12.
The Shell Script and Assembly File templates support shell scripts and assembly code, respectively. You
can run a shell script as part of a custom build. Assembly code is used for very specialized hardware-level
coding.
The Core Data templates include a Data Model file and a Mapping Model file. You can add these to pro-
jects that support Core Data. If your project doesn't use Core Data, you can ignore them. For details, see
Chapter 13.
Use the Rich Text File (RTF) and Strings File templates to add text-based data. The Strings file is used for
localization
—non-English language support. For details, see Chapter 12. The RTF file is a standard text
file. You can use it to hold any string- or text-based data. For OS X applications, you can use an RTF file to
define the information that appears in an application's About box.
Settings and Property Lists (plists) include an empty XML plist file for general property preferences and
settings. Both iOS and OS X applications already include an info.plist file with basic application details. The
iOS templates include a separate Settings Bundle, which uses an iOS-specific format to define an app's set-
tings and preferences.
Resource Rules and Entitlements are signed certificates that can be used to lock your application to spe-
cific hardware or software environments. For example, on iOS you can use these features to create an
ad
hoc build
that runs on specific handsets for beta testing, bypassing the app store. Entitlements and code-
signing are complex topics. For practical details, see Chapter 11.
You can use a Configuration Settings File to create your own list of build settings for a project—for ex-
ample, to create your own build setting defaults. For information about custom builds, see Chapter 12.
Deleting and renaming files
You can delete a file with the Delete key, or by right-clicking a file and selecting the Delete option from the con-
textual menu, as shown in Figure 5.7. When you delete a file, a dialog box appears asking you if you want to
remove it from the project and leave it on disk (“Remove Reference”) or move it to the trash. If you leave it on
