Sample Code
Switch branches/tags
Nothing to show
Clone or download
Erica Sadun Erica Sadun
Erica Sadun and Erica Sadun Bugfix for Touch with Alpha, courtesy of Dirk
Latest commit b8ca890 Mar 15, 2010
Failed to load latest commit information.
C02-Xcode Core Location Sep 15, 2009
C03-Objective-C Core Location Sep 15, 2009
C04-Building Interfaces Moving videos back to Aug 2, 2009
C05-ViewControllers Bugfix for Touch with Alpha, courtesy of Dirk Mar 15, 2010
C06-Views C13 and C14 Aug 5, 2009
C07-Images Bugfix for Touch with Alpha, courtesy of Dirk Mar 15, 2010
C08-Gestures Bugfix for Touch with Alpha, courtesy of Dirk Mar 15, 2010
C09-Controls Added infinite scroller to C09 (11X) but I'm really not happy with th… Dec 8, 2009
C10-Alerts Fixed small bug in 3.1.2 SDK, namely that normal hostname code breaks. Nov 30, 2009
C11-Tables Fixed error with CFAutorelease in ABContact Dec 3, 2009
C12-GameKit Updated all stringWithCString: to non-deprecated form Dec 3, 2009
C13-Networking Updated all stringWithCString: to non-deprecated form Dec 3, 2009
C14-Device Bugfix for Touch with Alpha, courtesy of Dirk Mar 15, 2010
C15-Media Adding readme for URL schemes Oct 5, 2009
C16-Push Bugfix for Touch with Alpha, courtesy of Dirk Mar 15, 2010
C17-CoreLocation Adding readme for URL schemes Oct 5, 2009
C18-Address Book Pushing search bar fixes via Jack Lucky Dec 3, 2009
C19-CoreData Fixed error with CFAutorelease in ABContact Dec 3, 2009
C20-StoreKit Updated hostname. Thanks, Gunnary Larisch Dec 3, 2009
C21-Grab Bag Adding readme for URL schemes Oct 5, 2009
.gitignore First Commit Apr 14, 2009
README.markdown Added README to repository Sep 24, 2009
cleanup Rough Cuts Initialization Jul 7, 2009
do-git First Commit Apr 14, 2009


iPhone Developer's Cookbook

Welcome to the source code repository for the 3.0 edition of the iPhone Developer's Cookbook. Sample code is never a fixed target. It continues to evolve as Apple updates its SDK and the CocoaTouch libraries. Get involved. You can pitch in by suggesting bug fixes and corrections as well as by expanding the code that's on offer. Github allows you to fork repositories and grow them with your own tweaks and features, and share those back to the main repository. If you come up with a new idea or approach, let us know. We'd be happy to include great suggestions both at the repository and in the next edition of this cookbook.

About the Cookbook

The iPhone Developer's Cookbook is written for experienced developers who want to build apps for the iPhone and iPod touch. It helps to be already be familiar with Objective-C, the Cocoa frameworks, and the Xcode Tools. That said, if you're new to the platform, this new edition of The iPhone Developer's Cookbook includes a quick-and-dirty introduction to Objective-C along with an intro to the Xcode Tools to help you quickly get up to speed.

Although each programmer brings different goals and experiences to the table, most iPhone developers end up solving similar tasks in their development work:

  • "How do I build a table?"
  • "How do I create a secure Keychain entry?"
  • "How do I search the Address Book?"
  • "How do I move between views?"
  • "How do I use Core Location and the iPhone 3GS's magnetometer?"

And so on. If you've asked yourself these questions, then this book is for you. The iPhone Developer's Cookbook will get you up to speed and working with the iPhone SDK, offering you ready-to-use solutions for the apps you're building today.

What's the deal with main.m?

For the sake of pedagogy, this book's sample code usually presents itself in a single main.m file. This is not how people normally develop iPhone or Cocoa applications, or should be developing them, but it provides a great way of presenting a single big idea. It's hard to tell a story when readers must look through 5 or 7 or 9 individual files at once. Offering a single file concentrates that story, allowing access to that idea in a single chunk.

These samples are not intended as stand-alone applications. They are there to demonstrate a single recipe and a single idea. One main.m file with a central presentation reveals the implementation story in one place. Readers can study these concentrated ideas and transfer them into normal application structures, using the standard file structure and layout. The presentation in this book does not produce code in a standard day-to-day best practices approach. Instead, it offers concise solutions that you can incorporate back into your work as needed.

Contrast that to Apple's standard sample code, where you must comb through many files in order to build up a mental model of the concepts that are on-offer. Those samples are built as full applications, often doing tasks that are related to but not essential to what you need to solve. Finding just those relevant portions is a lot of work. The effort may outweigh any gains.

There are two exceptions to this one-file rule. First, application-creation walkthroughs use the full file structure created by Xcode to mirror the reality of what you'd expect to build on your own. The walk through folders may therefore contain a dozen or more files at once.

Second, standard class and header files are provided when the class itself is the recipe or provides a pre-cooked utility class. Instead of highlighting a technique, some recipes offer these pre-cooked class implementations and categories (that is, extensions to a pre-existing class rather than a new class). For those recipes, look for separate .m and .h files in addition to the skeletal main.m that encapsulates the rest of the story.

How to build these projects

Before compiling, make sure you select a deployment target (such as Simulator 3.0 or Device 3.1) from the Project > Set Active SDK menu. All projects in this cookbook have been automatically stripped of specdific target details.

For the most part, the samples for this book use a single application identifier, com.sadun.helloworld. You will need to replace this identifier with one that matches your provision profile. This book uses one identifier to avoid clogging up your iPhone with dozens of samples at once. Each sample replaces the previous one, ensuring that SpringBoard remains relatively uncluttered. If you want to install several samples at once, simply edit the identifier, adding a unique suffix, such as com.sadun.helloworld.table-edits.