Well the reasons are actually different in the two books – and we really did not mean to mislead you. Let me start with this book.
The ideas for programming for your Mac and for the iPhone are mostly the same. If you are coming from a different platform/language than Cocoa/ObjC then the transition to programming the mac takes you most of the way to the iphone. There are some differences, of course. Some we can’t explicitly talk about. We can not take you through the APIs for the iPhone. Others we can talk about. For example, since automatic garbage collection is not supported on the iPhone we are careful to talk about referencing counting so that you can write iPhone apps as well.
So the reason I mention the iPhone is that I don’t want you to think that you are getting a book that tells you how to program the iPhone but we do cover many of the topics that will help you along.
For Core Animation the issue is a bit different. Bill Dudney was essentially done with his book in February and we could have had the book printed in time for WWDC. But Core Animation, although it is supported and works great on the Mac, was invented for the iPhone so we added an iPhone chapter to the book and retitled the book and were prepared to ship the book the day the iPhone NDA dropped. We assumed it would drop at WWDC, then when the iPhone store went live, then when iPhone 2.0 dropped, then maybe in September when push was added.
Arrrggghhhhh. It didn’t get dropped. So we are now puzzling with what to do about Bill’s book to be fair to people who have bought it already as well as being fair to Bill. If Apple doesn’t drop the NDA before we go to press with it we will certainly make the additional chapter available to anyone who has bought the book as a downloadable pdf. If the NDA never drops …
And, of course, we also have an iPhone SDK book that Bill co-wrote with Chris Adamson and Marcel Molina. We can’t publish that one either. It’s a very frustrating time to be sitting on so much great iPhone content and we really weren’t trying to mislead you. We’ve made guesses based on what we assumed Apple would “obviously” do.
I apologize if we’ve disappointed you with our (really my) miscalculations.