---

Strategies for Storing Interface Objects

You can strategically store an application’s interface objects in several nib files. When the application needs an interface object, you can load the nib file which contains it. You’ll conserve memory and improve program efficiency by following these guidelines:

• Store the main menu and perhaps a window in the main nib file. You should store a window in the main nib file only if the window always opens when the application starts up.

• Store each window or menu (such as an About window) that is likely to be used occasionally in a separate nib file. That way, you can call Interface Builder Services to load the window or menu only when a user requests it or when conditions warrant it.

• If your application uses a repeatable object, such as a word-processor document or a spreadsheet, store it in a document nib file. A document nib file is an auxiliary nib file that’s used as a template for a document: it contains the user interface objects and other resources needed to make a document.

---