xib - Nib file (and code) organization in a one-window, non-document-based app -

Good people of stack overflow,

I'm in the early stages of creating non-document-based cocoa The application that I am aiming for is a window layout similar to iTunes, in which there is a left, middle and right panel. The encoded template for this type of application includes a file named MainMenu.xib, which includes the main menu and the main application Window included, inherent in myApp_AppDelegate class With logic.

I can already be guessed that the route will eventually lead to a very large and random app representative class. Therefore, my clear sense tells me to break the argument in the main window for my NSWindowController subclass (and also the XIB file). Also, would I be right to divide each pane into my NSViewController subclass? It separates my worries better, to spend more files and some extra code to wire everything together.

The closest advice I can get is in Apple but it does not answer the question directly though, I think my question is not specifically about the Nib files, but the high-level application About the organization

Apparently the NSVU controller stuff is relatively new and yet well-documented is not.