Slashdot Mirror
Cocoa Programming for Mac OS X, 2nd Edition
The author is no stranger to OpenStep, having worked at NeXT as well as Apple in OpenStep application development and training. Currently, Hillegass teaches Cocoa programming for The Big Nerd Ranch.
Cocoa Programming for Mac OS X, 2nd Edition is written in a way that makes you feel like you are in a class. There are prerequisites you must know and understand before you can begin, and, as a good professor would, the author points out what you need to have and know before beginning. Happily, the author is quite meticulous and has generously provided useful resource links and help where readers may explore for their supplies and primers and the like.
Essentially, anyone with a copy of Mac OS X 10.3 Panther has all that should be required--the Developer Tools CD contains all developer software and documentation necessary (the author notes in the book specific locations for key primers and references).
If you are experienced in C++ or Java programming, Cocoa development will seem familiar enough. Objective-C is used throughout the book (the author notes that development in Java is possible, but not recommended) for the various and numerous exercises. Cocoa development is made easier with Apple's Xcode application, however, Cocoa is not for the timid or novice programmer. This book is well-written and easy to follow IF you have a respectable level of C/C++ or Java development under your belt.
The text, as well as its diction, is easy on the eyes and mind, and while this is a programming book, the author's voice speaks well, allowing you to feel as if you can ask the book questions as if you were in a classroom. Graphics and text are plentiful, but information is not packed on every page, so following along is far from drudgery. Each chapter does stack itself on information from the previous, so this isn't a reference book in the strictest sense.
Addison-Wesley, the publisher, has formatted the book nicely, with a pleasant font that won't tire the eyes, consistent code and text conventions, and a detailed Table of Contents and Index, However, it's thickness and binding doesn't lend itself to lying flat, so you'll have to weight the book pages down to read the book hands-free as you type in examples. Speciality bindings that could have been useful for this book are not cheap, based on my publishing experience, and such a binding would add more to the book's $45 US cost. (Amazon has a great deal on the book at the time of this review.)
Five new chapters were added in this 2nd edition, which discuss creating AppleScriptable applications, integrating OpenGL, adding Undo abilities, creating reusable frameworks, and tinkering with GNUStep, the raw open-source tools for those curious about making Cocoa apps under Linux.
If you're a UNIX or Windows developer who picked up a Mac OS X machine recently in hopes of developing new apps or porting your apps to Mac users. this book should be strongly considered as one of your essential reference and training tomes.
You can purchase Cocoa Programming for Mac OS X, 2nd Edition from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, carefully read the book review guidelines, then visit the submission page.
in realated news Dutch cocoa maker Godiva comes out with a book on properly programming your microwave to make the perfect drink.
Sig (appended to the end of comments you post, 120 chars)
Real men code everything in BASIC.
I'll wait for the third edition: Protocol Handler Exploit Programming for Mac OS X.
taken! (by Davidleeroth) Thanks Bingo Foo!
kookoo for Cocoa Progs
Real men code everything in assembly
Evolution or ID?
This one goes up to 11.
the cocoa, cocoa cabana....
Evolution or ID?
"How different is this one from the first edition?"
Brushed Metal pages?
-m
#
# Modus Ponens
#
Real men don't care WHAT the real answer is...instead, they choose one at random and beat the shit out of anyone who disagrees.
Which is why true && false == true. What, you wanna start? BRING IT ON!
Hey freaks: now you're ju
Real Programmers don't write specs -- users should consider themselves lucky to get any programs at all, and take what they get.
Real Programmers don't comment their code. If it was hard to write, it should be hard to understand.
Real Programmers don't write application programs, they program right down on the bare metal. Application programming is for feebs who can't do system programming.
Real Programmers don't eat quiche. They eat Twinkies. And Szechwan food. (Do not go to eat Szechwan food with a group of Real Programmers unless you are prepared to argue bitterly over the last spring roll.)
Real Programmers aren't scared of GOTOs... but they really prefer branches to absolute locations.
Real Programmers don't write COBOL. COBOL is for wimpy application programmers.
Real Programmers' programs never work right the first time. But if you throw them on the machine they can be patched into working in "only a few" 30-hour debugging sessions.
Real Programmers don't write in FORTRAN. FORTRAN is for pipe stress freaks and crystallography weenies.
Real Programmers never work 9 to 5. If they are around at 9 AM, it's because they were up all night.
Real Programmers don't write in BASIC. Actually, no programmers write in BASIC... after age twelve.
Real Programmers can take the scissors off the phone cord.
Real Programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN.
Real Programmers don't play tennis, or any other sport which requires you to change clothes. Mountain climbing is OK, and Real Programmers wear their climbing boots to work in case a mountain should suddenly spring up in the middle of the computer room.
Real Programmers don't do documentation. Documentation is for simps who can't figure out the listing.
Real Programmers don't write in PASCAL, or BLISS, or ADA, or any of those pinko computer science languages. Strong typing is for people with weak memories.
Ah, so they have Java and Cocoa now, eh? In that case, I have just one question for you:
Cream or sugar?
* Perhaps today is a good day to die... I say we ship it."
* Specifications are for the weak and timid!!
* This machine is a piece of GAGH! I need dual Pentium (!) processors if I am to do battle with this code.
* You cannot really appreciate Dilbert unless you've read it in the original Klingon.
* Indentation?! I will show you how to indent when I indent your skull!
* What is this talk of 'release'? Klingons do not make software 'releases'. Our software escapes, leaving a bloody trail of designers and quality assurance people in its wake!
* Klingon function calls do not have "parameters" - they have "arguments"- and they ALWAYS WIN THEM.
* Debugging? Klingons do not debug. Our software does not coddle the weak.
* I have challenged the entire Quality Assurance team to a Bat-Leh contest! They will not concern us again.
* A TRUE Klingon warrior does not comment his code.
* By filing this bug report you have challenged the honor of my family. Prepare to die!
* You question the worthiness of my code? I should kill you where you stand!
* Our users will know fear and cower before our software! Ship it! Ship it and let them flee like the dogs they are!
(sources too numerous to attribute)
---anactofgod---
---anactofgod---
"Equal opportunity swindling - *that* is the true test of a sustainable democracy."
What is the big deal surrounding MVC for a GUI?
And that, my young padawan, is why you fail.