{"id":447,"date":"2003-05-18T19:12:11","date_gmt":"2003-05-18T23:12:11","guid":{"rendered":"\/?p=447"},"modified":"2025-07-03T18:53:49","modified_gmt":"2025-07-03T22:53:49","slug":"mac_os_x_advanced_develop","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2003\/05\/18\/mac_os_x_advanced_develop\/","title":{"rendered":"Mac OS X Advanced Development Techniques"},"content":{"rendered":"

\n\nSteven Frank<\/a> and Buzz Andersen<\/a> like this new book<\/a> by Joe Zobkiw. I’m not really a fan of it, though.\n\n<\/p>\n\n\n\n

\n\nThe book begins by repeating the annoying<\/a> assertion that “The Cocoa application environment is the native Mac OS X development environment” (page 14).\n\n<\/p>\n\n\n\n

\n\nPage 17 exhorts you to “read Apple’s Human Interface Guidelines and practice them,” but on page 40 the book directs you to create a metal application that has no business<\/a> being metal, and page 61 includes a hideous example of excessive group boxes<\/a>.\n\n<\/p>\n\n\n\n

\n\nPage 22 demonstrates scalar accessor methods by…creating an infinite loop.\n\n<\/p>\n\n\n\n

\n\nPage 56 characterizes Cocoa’s reference counting system as a “big gotcha.” It doesn’t explain retaining and releasing particularly well, nor does it link to more comprehensive coverage<\/a>.\n\n<\/p>\n\n\n\n

\n\nPage 63 uses the application controller’s +initialize<\/code> method to set the application’s defaults if they have not already been set. It uses an integer where a boolean would be a better fit, and it creates NSNumber<\/code> objects instead of just using -setInteger:forKey:<\/code>. More seriously, the example probably should have used -registerDefaults:<\/code> instead of actually setting the defaults.\n\n<\/p>\n\n\n\n

\n\nPage 73 says “pop-up menu” when it means “contextual menu.”\n\n<\/p>\n\n\n\n

\n\nIn a great example of the book’s cursory coverage, page 126 recommends embedding frameworks in your application’s bundle without mentioning that the key to doing this is to use the magic @executable_path\/..\/Frameworks<\/tt> string for the installation path. It merely tells you to use Project Builder’s stationery, which is pre-configured for the framework being in the Library<\/tt> folder.\n\n<\/p>\n\n\n\n

\n\nPages 143 and 158–160 use CFPreferences<\/code> (and other Core Foundation stuff) rather than NSUserDefaults<\/code> (and other Cocoa stuff) in a Cocoa example without explaining why.\n\n<\/p>\n\n\n\n

\n\nPage 155 says to give your .prefPane<\/tt> package a custom icon by copying from the .icns<\/tt> file’s Get Info window and pasting into the Get Info window of the .prefPane<\/tt>. First, this won’t work. You want to copy the contents of the .icns<\/tt> file, not its icon. Second, you’d have to re-do this process after each clean build. It would be better to use Project Builder to set the icon using the Info.plist<\/tt> file. Now, maybe there’s some reason this doesn’t work with .prefPane<\/tt>s, but if this is the case the book should say so.\n\n<\/p>\n\n\n\n

\n\nPage 163 says that status items “are intended to display hardware or network status\/settings only. This is why you will see iChat and Airport[sic] but not Mail.app.” Now there’s a clear distinction.\n\n<\/p>\n\n\n\n

\n\nPage 169 creates a menu using [[[NSMenu alloc] init] retain]<\/code> and only releases it once, thus leaking it.\n\n<\/p>\n\n\n\n

\n\nThe Threads chapter is basically an introduction to what threads are. It doesn’t really talk about Cocoa thread-safety, and in fact the examples are thread-unsafe. Nor does it mention how to communicate between different threads.\n\n<\/p>\n\n\n\n

\n\nThe Terminal (NSTask<\/code>) chapter doesn’t really add anything beyond Apple’s documentation and sample code. It doesn’t discuss buffering issues, which are probably the biggest gotcha here. It’s also not a good example to emulate: it uses polling, it doesn’t protect a shared variable with locks, and it calls the AppKit from a child thread. For some unknown reason, all of the threads end with calls to [NSThread exit]<\/code>, even though the book ascribes no benefit to this practice.\n\n<\/p>\n\n\n\n

\n\nThe XML-RPC chapter has some information that’s not in other Mac books to my knowledge. However, it contains this confusing bit of code:\n\n<\/p>\n\n\n\n

\n\n\/\/ Add the users choices to the dictionary to be passed as parameters\n\nparams = [NSMutableDictionary dictionaryWithCapacity:2];\n\n[params setObject:selectedProduct forKey:selectedProduct];\n\n[params setObject:selectedColor forKey:selectedColor];\n\n\n\n\/\/ Create the array to specify the order of the parameter values\n\nparamsOrder = [NSArray arrayWithObjects:selectedProduct, selectedColor, nil];\n\n<\/pre>\n\n\n\n
\n\nI would have made the keys and array elements string constants like @\"ProductColor\"<\/code> and @\"ProductProduct\"<\/code>. Not only does that make the intent clearer, but it won’t fail if a color and a product have the same name.\n\n<\/p>\n\n\n\n
\n\nAnd the next page goes on to release params<\/code> and paramsOrder<\/code> both of which were already autoreleased. The subsequent SOAP chapter does use readable string keys, but it has the same over-releasing bug.\n\n<\/p>\n\n\n\n
\n\nPage 298 promises to help find “Application Support Directories,” but apparently the  “Application Support” folder isn’t one of them. It would have been better to provide some alias-savvy code for locating and creating the application’s folder in ~\/Library\/Application Support<\/tt>.\n\n<\/p>\n\n\n\n
\n\nPage 300 uses NSOKButton<\/code> instead of NSAlertDefaultReturn<\/code>. Luckily, the constants have the same value so the code does work.\n\n<\/p>\n\n\n\n
\n\nPage 301 again over-retains an NSMenu<\/code>.\n\n<\/p>\n\n\n\n
\n\nAlthough there are a lot of errors (and more typos) in this book, I sympathize. It’s tough to get all the details right, and many technical books do no better. However, my larger concerns are the choice of topics and the depth of coverage.<\/p>\n\n\n\n
\n\nDon’t let the title fool you. This is not an advanced book, nor is it about techniques. Instead, it’s a guided tour through some example projects that are off the beaten path. Many of them are covered in other books and articles, but some are not. Thus, it’s great that this book exists, but it will not be of interest to everyone. The advanced book I was hoping<\/em> to find, would cover things like AppleScript, inter-thread communication and threaded application architectures, application code structure, databases and persistence, AppKit gotchas, third-party libraries and wrappers, medium- and lower-level networking, Quartz tricks, and optimization.\n\n<\/p>\n\n\n\n
\n\nCocoa Programming<\/a> by Anguish, Buck, and Yacktman is both wider and deeper than this book. Not only does it have great introductory material (for those who know how to program but don’t know Cocoa), but it also contains a lot more advanced information. Every Cocoa programmer should own this book. Its only significant flaw is ignoring AppleScript—as do all the other Cocoa books I’ve seen.\n\n<\/p>\n\n\n\n
\n\nMac OS X Advanced Development Techniques<\/cite> does contain chapters on Carbon<\/a> and Cocoa<\/a> plug-ins and on XML-RPC and SOAP<\/a>. I don’t know of other books that cover these, but Apple (see preceding links) and O’Reilly<\/a> have already done a decent job.\n\n<\/p>\n\n\n\n
\n\nI hope someone will step in and write a truly advanced book about Mac OS X programming. Until then, I recommend Apple<\/a> and Omni<\/a>’s mailing lists, Mulle kybernetiK<\/a>,\n\nO’Reilly<\/a>, Stepwise<\/a>, and developer blogs.\n\n<\/p>","protected":false},"excerpt":{"rendered":"
Steven Frank and Buzz Andersen like this new book by Joe Zobkiw. I’m not really a fan of it, though. The book begins by repeating the annoying assertion that “The Cocoa application environment is the native Mac OS X development environment” (page 14). Page 17 exhorts you to “read Apple’s Human Interface Guidelines and practice […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"apple_news_api_created_at":"2025-07-03T22:53:13Z","apple_news_api_id":"2f58b917-5c10-4496-86eb-57a889ec4979","apple_news_api_modified_at":"2025-07-03T22:53:51Z","apple_news_api_revision":"AAAAAAAAAAAAAAAAAAAAAQ==","apple_news_api_share_url":"https:\/\/apple.news\/AL1i5F1wQRJaG61eoiexJeQ","apple_news_coverimage":0,"apple_news_coverimage_caption":"","apple_news_is_hidden":false,"apple_news_is_paid":false,"apple_news_is_preview":false,"apple_news_is_sponsored":false,"apple_news_maturity_rating":"","apple_news_metadata":"\"\"","apple_news_pullquote":"","apple_news_pullquote_position":"","apple_news_slug":"","apple_news_sections":"\"\"","apple_news_suppress_video_url":false,"apple_news_use_image_component":false,"footnotes":""},"categories":[4],"tags":[2786,63,71],"class_list":["post-447","post","type-post","status-publish","format-standard","hentry","category-programming-category","tag-aliases","tag-book","tag-programming"],"apple_news_notices":[],"_links":{"self":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/447","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/comments?post=447"}],"version-history":[{"count":1,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/447\/revisions"}],"predecessor-version":[{"id":48332,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/447\/revisions\/48332"}],"wp:attachment":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/media?parent=447"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/categories?post=447"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/tags?post=447"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n\nThe book’s coverage is wide and shallow. It’s based around a series of examples, and it’s wont to show a simple code example and then paraphrase the code in prose. As a result, in many cases I felt it didn’t add much value over Apple’s documentation and sample code. I would have liked to see less focus on what<\/em> and more on why<\/em>. Also, if a book is based around examples, I would expect them to exhibit best practice techniques. In contrast, Bill Cheeseman’s Cocoa Recipes<\/a> manages to use an example-driven style without ignoring the rationales, subtleties, and gotchas.\n\n<\/p>\n\n\n\n