"IOS Human Interface Guidelines"--container View Controller

Container View Controller

The container View Controller manages and presents its collection of child views--or a collection of child controllers--in a way that it defines itself.

Examples of system-defined container View Controllers are tab bar view controllers, navigation bar view controllers, and column view controllers (View tab bar, Navigation bar, and Split view controller to learn many other things about these elements).

API NOTE

View Uiviewcontroller Class Reference Learn about defining your own defined container view controller content in your code.

The container view controller has no pre-defined appearance and behavior.

Use the container view controller to navigate through the presentation in a way that you define.

asking yourself if a container view controller you define is really necessary. the user is accustomed to the appearance and behavior of the standard container view controller. For example, the column view controller and the tab bar View Controller.

You need to make sure that the potential benefits of the container view you define are greater than the fact that the user may not find or immediately know how it works.

Make sure that you define your own container view controller to work in all directions. It is important to design a container view controller that gives users a consistent experience in both vertical and horizontal directions.

generally speaking. Avoid a brilliant view transition. When you use the story version to design your own defined view controller, it's easy to define your own defined transitions between views.

But in most cases. A brilliant view transition shifts people from their tasks and often reduces the beauty of your app's display.

This article is translated from the official Apple development document to view the integration set: Https://github.com/Cloudox/iOS-Human-Interface-Guidelines All rights reserved: Http://blog.csdn.net/cloudox_

"IOS Human Interface Guidelines"--container View Controller