Question

I’m working on an iPhone app that (among other things) has a detail view for records with lots of attributes and lots of related records. Rather than having one really long scroll view or table view, I am thinking it might be easiest to break the detail view into several separate views (some UIViews, some UITableViews, etc) that each display one grouping of the record’s attributes or related records.

I use a UINavigationController to control view changes in my app, and I could put a UISegmentedController the toolbar to control which group of the record’s attributes or relationships to display. This would look like:

I’m thinking this is the best way to go, but how do I populate the Content Area without pushing and popping from the navigation controller?

Is this even the “right” way to do this? Is this needlessly complex? Or is there some native controller that I should be considering instead?

Thanks!

Answer 1

That would be fine, I think. You’d have a view controller class roughly like:

@interface MyDetailViewController : UIViewController {
    // a blank, full-area view that will serve as the superview for modeSelector
    //     and your detail views
    UIView *rootView;

    UISegmentedControl *modeSelector;

    // placeholder to track the current view, not strictly necessary.
    UIView *currentDetailView;

    UIView *firstModeView;
    UIView *secondModeView;
    // ... etc.
}

You’d probably store each UIView composition in its own nib, and load them manually with [NSBundle loadNibNamed:owner:options:].

Add IBActions to your view controller to show each view:

-(void)showSecondModelView:(id)sender {
    if(currentDetailView != secondModeView) {
        [self.rootView addSubview:secondModeView];

        // alternatively, you could keep all of your detail views
        //     on the root view, and use bringSubviewToFront
        [self.currentDetailView removeFromSuperview];
        self.currentDetailView = secondModeView;
    }
    return;
}

Connect your actions in IB or with [modeSelector addTarget:action:forControlEvents] and you should be good to go.