Apologies if this has been asked before. I searched and couldn't find it.
In my application I have about 10 nib files, most of which hold a single significant view object and a number of subviews/controls.
At what point would you consider breaking nibs into pieces? For example in one of my nibs I have an NSCollectionview and the prototype view (relatively simple) in the same nib. Would you put the prototype view in a separate nib?
To me there is a clear tradeoff. If you subdivide too much then you lose many of the advantages of Interface builder (arranging things geometrically, setting resize masks etc), and you need to write more code to ensure pieces of views are arranged properly. On the other hand if you put everything into one nib ... well .. we all know that is a refactoring nightmare, slow loading etc.
So how do you decide when to draw this line? Looking at my own code I think I've used the following;
(a) Always split pieces that don't always need to load together
(b) Never put more than one relatively complex control (eg NSTableview, NSCollectionview etc) in a nib
Edit: -- I should say that I sometimes break these rules. For example I have a window for configuring a certain type of object. It has a complete Master-detail interface with an NSTableview (master) and a bunch of text fields (detail). I guess this violates my one complex view per nib rule.
What rules do you use?