Compras Nikon Bluetooth |
It's in explaining novice-level material that Sydow shines most. He starts, as is traditional, with a "Hello World" application that introduces Project Builder, Interface Builder, and nib resource files. He combines Carbon source code listings with lots of text and a fair number of screen shots, and though there's no companion CD-ROM, you can download the code from the Web (this approach increases the likelihood that you'll get error-free examples to learn from). Sydow explains everything he does with Carbon code--he frequently builds one application, then expands or modifies it--so time spent reading his explanations is well rewarded. Plan to experiment with the contents of the Mac OS Developer Tools disk (the one that came with your copy of the operating system) using this book as your guide. --David Wall
Topics covered: The fundamentals of programming in the Cocoa language for Mac OS X, as well as aspects of that operating system that will be new to experienced Mac OS developers. The author puts emphasis on creating projects (under Project Builder) and graphical user interfaces (under Interface Builder), as well as windows, menus, other user interface elements and the event handlers that react to their manipulation. There's excellent coverage of localization techniques, programmatic QuickTime movie manipulation, and techniques for porting Mac OS 8 and 9 apps to Mac OS X.
This is the book's strength and weakness. As an experienced programmer and someone who has dabbled with Mac programming for years I found the pace of the book plodding and repetitive. I wished for a little less coverage on each topic so there would be room for more topics. But this will certainly stay on my shelf since, for those topics that were covered, I know I will be able to turn back and find fully worked out examples and explanations for these routines basic usage.
But now I need to figure out what to read next to become a better Carbon programmer, besides, of course, Apple's reference documentation.
BEWARE! Before buying this book, check to see if you can get the example code as the book does NOT come with an accompanying CD.
The book is easy to read with great examples. It's the perfect starting point if you have a Mac OS application that needs to be converted to Carbon.
In the Editorial review, we read:
"You'll also find this book moderately handy if you're already a Mac programmer and want a gentle introduction to Cocoa, the new programming facilities that Mac OS X exposes. Even if you've used your experience to figure out Cocoa on your own, you'll probably like Dan Parks Sydow's coverage of porting old code to the new environment, and of new multimedia programming capabilities."
But I guarantee you, if you figured out Cocoa on your own, this book will be a slap in the face, especially if you believed what I just quoted and bought the book on the strength of that belief.
Listen to the author, who did write a pretty handy Carbon programming book:
[This book will] "help you make the transition from using the original Macintosh Toolbox API to using the Carbon API." (p. xiii). Or, "Because most Mac programmers use a procedural programming language rather than an object-oriented language, and because Cocoa applications don't run on non-Mac OS X computers, the focus of this book is on Carbon rather than Cocoa." (p. 19)
And there you have it. Sydow explains Cocoa just enough to tell you he isn't going to talk about it any more. If you are an OO programmer looking to learn Cocoa, this isn't your book. If you are an old (or young) Toolbox programmer looking to move to Carbon, you'll probably like it. Somebody decided that using the word "Cocoa" would sell more copies. Shame on you. May you feel a sting equal to lost weight of my wallet.
On another subject, other than the book "MySQL" by Paul DuBois, which is awesome, every other New Riders title I've bought has ... They are generally disorganized-take for example, "PHP Web Application Development" and the book I reviewed here. Both follow a kind of rambling style that is virtually useless for the busy professional. Enough said. Sorry.
Is knowledge knowable? If not, how do we know that?
This is the theory that Jack built.
This is the flaw that lay in the theory that Jack built.
This is the palpable verbal haze that hid the flaw that lay in...