I’ve done a fair bit of Cocoa over the past few years mostly based off learning from Hillegass’s book. I recently felt like I needed to learn some of the basics again (after watching Bill Dudney’s iPhone videos), so I bought your Cocoa Programming book. I read through chapter 1 and decided it might be a bit too basic, so I started going through Hillegass’s book again (this time the 3rd edition).
However, after reading your answers to a few posts here and looking again at your book’s table of contents, I’m not so sure where your book falls in. Initially I saw just the 8 chapter headings and read the multiple references to “this book is not comprehensive” in chapter 1 which led me to believe the book was going to be very basic.
So here are my comments on chapter 1.
Perhaps you are being a little too strong on it being a basic book. I’m guessing that you’ll cover all of the essentials to creating a Cocoa application (sheets, views, saving data, etc.), but you won’t cover every API. So by the end of the book I’ll know how to create a small/medium Cocoa application (I’m thinking something like NetNewsWire, MoneyWell, Transmit, TextMate, etc.) either through direct learning from the book or knowing where to look after reading the book, i.e. when I finish the book will I be needing Advanced Cocoa Programming to fill in gaps or will I just need specific detailed questions answered. Your analogy left me thinking that all I’ll learn is where to look stuff up. I want more than “a feel for the neighborhood” and I think the book will deliver. It’s like you learn a lot about the neighbors, enough to know how they can help you, what they can do for you, but you don’t know all the sordid details of their lives. I’m just not sure how to say that any better.
I guess I’m not sure where your book fits compared to Hillegass’s book. Is it aiming for the same audience? More basic? I know Marcus is going to cover Core Data in depth and Dudney has covered Core Animation and another group is covering iPhone. Perhaps this is the pragprog version of Hillegass’s book? Perhaps it needs a stronger section on who the expected audience is (without directly comparing to another title, of course).
Should there be a section on what you need to know? How much C do I need? What if I know Java or C++, is that enough? How about if I’ve never programmed before, should I start with another book first?
I’m thinking of the person who picks the book up in the store and wants to find out if it’s for them in < 5 minutes. I can usually tell based on the prerequisites and goals if the book is going to fit for me. I’m much more interested in what I’m going to learn from the book and that it’s aimed at my level than I am in how well it is written.
I know this is wordy and not well communicated. I’ll keep reading and check back.