[链接]Creating Custom Container View Controllers

Creating Custom Container View Controllers

https://developer.apple.com/library/ios/featuredarticles/ViewControllerPGforiPhoneOS/CreatingCustomContainerViewControllers/CreatingCustomContainerViewControllers.html

Implementing a Custom Container View Controller

Once you’ve designed your class’s behavior and determined many aspects of its public API, you are ready to start implementing the container. The goal of implementing a container is to be able to add another view controller’s view (and associated view hierarchy) as a subtree in your container’s view hierarchy. The child remains responsible for its own view hierarchy, save for where the container decides to place it onscreen. When you add the child’s view, you need to ensure that events continue to be distributed to both view controllers. You do this by explicitly associating the new view controller as a child of the container.

The UIViewController class provides methods that a container view controller uses to manage the relationship between itself and its children. The complete list of methods and properties is in the reference; see “Managing Child View Controllers in a Custom Container” in UIViewController Class Reference

Important: These UIViewController methods are only intended to be used to implement container view controllers; do not call them in a content view controller.

Adding and Removing a Child

Listing 14-1 shows a typical implementation that adds a view controller as a child of another view controller. Each numbered step in the listing is described in more detail following the listing.

Listing 14-1  Adding another view controller’s view to the container’s view hierarchy

- (void) displayContentController: (UIViewController*) content;

{

[self addChildViewController:content]; // 1

content.view.frame = [self frameForContentController]; // 2

[self.view addSubview:self.currentClientView];

[content didMoveToParentViewController:self]; // 3

}

Here’s what the code does:

1. It calls the container’s addChildViewController: method to add the child. Calling the addChildViewController: method also calls the child’swillMoveToParentViewController: method automatically.

2. It accesses the child’s view property to retrieve the view and adds it to its own view hierarchy. The container sets the child’s size and position before adding the view; containers always choose where the child’s content appears. Although this example does this by explicitly setting the frame, you could also use layout constraints to determine the view’s position.

3. It explicitly calls the child’s didMoveToParentViewController: method to signal that the operation is complete.

Eventually, you want to be able to remove the child’s view from the view hierarchy. In this case, shown in Listing 14-2, you perform the steps in reverse.

Listing 14-2  Removing another view controller’s view to the container’s view hierarchy

- (void) hideContentController: (UIViewController*) content

{

[content willMoveToParentViewController:nil]; // 1

[content.view removeFromSuperview]; // 2

[content removeFromParentViewController]; // 3

}

Here’s what this code does:

1. Calls the child’s willMoveToParentViewController: method with a parameter of nil to tell the child that it is being removed.

2. Cleans up the view hierarchy.

3. Calls the child’s removeFromParentViewController method to remove it from the container. Calling the removeFromParentViewController method automatically calls the child’s didMoveToParentViewController: method.

For a container with essentially static content, adding and removing view controllers is as simple as that. Whenever you want to add a new view, add the new view controller as a child first. After the view is removed, remove the child from the container. However, sometimes you want to animate a new child onto the screen while simultaneously removing another child. Listing 14-3 shows an example of how to do this.

Listing 14-3  Transitioning between two view controllers

- (void) cycleFromViewController: (UIViewController*) oldC

toViewController: (UIViewController*) newC

{

[oldC willMoveToParentViewController:nil]; // 1

[self addChildViewController:newC];

newC.view.frame = [self newViewStartFrame]; // 2

CGRect endFrame = [self oldViewEndFrame];

[self transitionFromViewController: oldC toViewController: newC // 3

duration: 0.25 options:0

animations:^{

newC.view.frame = oldC.view.frame; // 4

oldC.view.frame = endFrame;

}

completion:^(BOOL finished) {

[oldC removeFromParentViewController]; // 5

[newC didMoveToParentViewController:self];

}];

}

Here’s what this code does:

1. Starts both view controller transitions.

2. Calculates two new frame positions used to perform the transition animation.

3. Calls the transitionFromViewController:toViewController:duration:options:animations:completion: method to perform the swap. This method automatically adds the new view, performs the animation, and then removes the old view.

4. The animation step to perform to get the views swapped.

5. When the transition completes, the view hierarchy is in its final state, so it finishes the operation by sending the final two notifications.