• Hello list. I've been playing with the NSViewController class introduced
    with Leopard and it seems the common way to use is it to create a NIB
    containing the view, set the FileOwner as the NSViewController instance, and
    connect the single outlet to the view. Then you call [initWithNib:...] to
    load that nib file plus view. I have a list of classes that must provide
    their own views (for cells in a list) but I don't want to have inidividual
    nib files for 20+ views. What I would like is to create a single NIB
    containing all my views to be loaded at runtime.

    What's the best way to handle this situation? I could make the views
    subviews of a single view and pull them out after the superview is loaded
    but that means mainting one big superview in the nib with loads of subviews.
    Alternatively, I could create NSViewControllers with [init] and [setView]
    for each view but that seems to defeat the usefullness of the class.

    I'm probably missing something here but I can't find much documentation on
previous month december 2007 next month
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
Go to today