Overall a very good book but has the usual technical errors.

I am currently more than halfway through this book now and already I can say that I am very happy with my purchase.

Firstly, this is not a programming how-to book. Plus, I don't think it should be your first Mac development book. The purpose of this book is to provide you with a solid understanding of the Xcode tool and to teach you some smart application design methods. I recommend that you start reading this book already knowing some Objective-C and Cocoa (at least a little anyway) because you will take with you so much more than just how to use the Xcode tool. Actually, without any Cocoa programming knowledge, you may just end up confused. The reason I say this is because the examples use intermediate to advanced Cocoa programs to illustrate Xcode as you advance through the book.

This book starts you off with some background information about what happens when you compile a Cocoa application, how the runtime system works and some basic debugging skills. It then instructs the reader to build a command line tool which eventually buds into a mature Cocoa application as the chapters go by, each chapter adding a major feature to the application while introducing additional Xcode features as you go. Some of the Xcode features that I've already learned include: Including a command line tool in a project as a target dependency, how to build and include a static BSD library in a project, using Text Macros to add language-specific code patterns to the Xcode menus, I've expanded my knowledge of Cocoa bindings, how to include a framework target, working with dynamic libraries and more.

Follow the examples! I was actually pleasantly surprised at the Cocoa skills I've learned simply from the examples' code. They are not typical. I've already assimilated the following intermediate to advanced Cocoa programming skills: Calling a command line tool from a Cocoa app using pipes and tasks, building and calling functions from a BDC static library, design skills that promote code decoupling and mixing C and Obj-C conventions together.

I do have some gripes: Technical errors! I've never written a book but how difficult is it to make sure that the samples work once you reach the end of a chapter? And I'm not talking about the intentional errors the author left in the code that are later fixed. For example, in one chapter the book instructed me to add 3 object controllers in Interface Builder. By the end of the chapter the program didn't run because I was never instructed to configure one of the three controllers. I went back to make sure I didn't miss anything. I was able to figure it out myself after some time (another reason you should not be a newbie reading this book) but this error and others should not have made it into the book. Don't authors proof read their own work or at least have a couple of other people read the book and try out the examples? Sheesh!

Also, be warned. I have yet to find any errata or contact info for the author for this book. So if you need help, you may not find any.

This book is an easy read. No nonsense and straight to the point. Most chapters are between 10 and 20 pages, which provides you with plenty of opportunity to stop, rest and take in what you've just read.

I wanted to rate this book ***1/2 for the errors and lack of help, but I can't give half-stars here. This book doesn't deserve 3 stars, so I gave it a 4.

Note [16-MAR-2006]: Wouldn't you know it, I just found the official Step Into Xcode web site complete with downloadable code, errata and author contact info! Here it is: http://six.manoverboard.org/ I now officially increase this books rating from ***1/2 to ****. :)

Other Reviews

• Poor Introductory Reference
• Not a good introduction to anything.
• Lays a great foundation
• Lots of useful info.
• Overall a very good book but has the usual technical errors.