I have a UIViewController that is loading several subviews at different times based on user interaction. I originally built all of these subviews in code, with no nib files. Now I am moving to nib files with custom UIView subclasses.

Some of these subviews display static data, and I am using loadNibNamed:owner:options: to load them into the view controller. Others contain controls that I need to access.

I (sort of) understand the reasons Apple says to use one view controller per screen of content, using generic controller objects (NSObjects) to manage subsections of a screen.

So I need a view controller, a generic controller, a view class and a nib. How do I put this all together?

My working assumptions and subsequent questions:

• I will associate the view class with the nib in the 'class identity' drop down in IB.
• The view controller will coordinate overall screen interactions. When necessary, it will create an instance of the generic controller.
• Does the generic controller load the nib? How?
• Do I define the outlets and actions in that view class, or should they be in the generic controller?
• How do I pass messages between the view controller and the generic controller?

If anyone can point me to some sample code using a controller in this way, it will go a long way to helping me understand. None of the books or stackoverflow posts I've read have quite hit the spot yet.