Xcode – n easy to understand guide (new to Cocoa, Xcode, etc) for Interface Builder that talks about proxy objects

cocoacocoa-touchinterface-builderxcode

Back in the day of C/C++, the part of the language that really hung me up was pointers. I understand them now, of course.

Now, Interface Builder Proxy Objects or more importantly, how to use Interface Builder and what to put in the .XIB window (window that contains the File's Owner, First Responder, etc…) for a given XIB.

I've gone through quite a few examples from books and samples found both in Xcodes examples and around the web. They have been helpful, but I still feel a little lost.

I feel that understanding IB is very important to understanding how to write Mac/iPhone/iPod touch applications.

I have gone through the following resources so far:
Aaron Hillegass' Cocoa Programming for Mac OS X
Pragmatic Programmer resources:
Becoming Productive in Xcode (screencast)
Cocoa Programming
Coding in Objective-C 2.0 (screncast)
Writing Your First iPhone Application (screencast)
iPhone SDK Development

I've also gone over the Interface Builder Users Guide PDF from Apple.

Any suggested tips/resources will be appreciated!

Best Answer

First, placeholder is a better word than proxy here.

Normally when you have an object in a NIB/XIB file it means that loading the NIB file will create that instance. The placeholder objects are objects that will already exist when the NIB file is loaded, and they appear inside of the NIB so that you can make connections between the objects that will be created by loading the NIB and the objects that already exist.

The file's owner, first responder and application are all placeholders.

The file's owner is placeholder for the object that will load the nib. All of the NIB loading methods take an 'owner' parameter. When you make a connection with the File's owner, when it's established at runtime, it will be connected to the owner object passed in to the nib loading method. Many UIKit and AppKit classes invoke the nib loading methods for you. NSApplication, NSViewController, NSWindowController, UIApplication, and UIViewController all load NIB files on your behalf. When they do that they pass self as the owner parameter to the nib loading methods. That's why when you use a view controller or a window controller you set the file's owner to your subclass and make most of the connections between your views and the file's owner.

The NSApplication instance is a simple placeholder for [NSApplication sharedApplication]. That's a global singleton and the icon in Interface Builder represents that global singleton. Loading the NIB file does not create a second NSApplication instance. By contrast, when a NIB file contains a window, if you load it a dozen times, you'll have a dozen window instances, but still one NSApplication instance.

The first responder is unique. Connecting an action to the first responder means that when the action is fired, it should dynamically be sent to the responder chain. The responder chain typically starts with the focused view, and continues up through the view hierarchy and includes some controllers and delegates. Each object in the chain gets a shot at handling the action. Menu items work great with the responder chain. If you had a menu item for "Make Bold" that is supposed to make the currently selected text bold, you might start by hooking that up to an NSApplication subclass, but then you'd have to know all of the situations that "Make Bold" applies, and how to handle them. A text view and an editable web view would probably need different code to handle "make bold" and bottling this all up in one object would get quite complex and wouldn't be very extensible. Instead you could connect the "Make Bold" menu item's action up to a makeBold: action on the First Responder. This would mean that when the menu item was selected, the focused object, or one of its parents that responded to makeBold:, would get the makeBold: message. Now many classes can implement a makeBold: method and respond to this menu item when they're in focus.

Related Topic