Column View Controller
The column view controller is a full-screen view controller that manages the presentation of two child view controllers.
API NOTE
Each sub-view of the column view Controller is responsible for the display management of one panel. The columns View controller displays these child view controllers themselves and manages transitions in different directions. Check out the Uisplitviewcontroller Class reference and Split view controllers to learn more about defining the contents of the column view controller in your code.
In iOS 7 and earlier systems, the split view controller can only be used on ipad.
By default, a column view controller uses the current size to determine how to schedule its child view controllers. For example, a column view controller:
- Try to display two panels side by side in a horizontal normal environment
- You can display the main panel at the top level of the second panel, or you can hide the main panel from the outside of the screen until it is needed, usually in a horizontal compact environment
You can influence panel scheduling by requiring the column view controller to prioritize your particular layout in a specific display environment.
A column view controller can contain a wide range of objects and views, such as:
- Lists, pictures, maps, text, Web pages, or custom views
- Navigation bar, toolbar, or tab bar
NOTEEven though the main panel is often referred to as Master pane, the second panel is often referred to as Detail pane, which is not mandatory in the code.
Use the column view controller to display persistent information in the main panel, and display the relevant details or dependent information in the second panel. In this design mode, when people select an entry in the main panel, the second panel should display information about this entry. (You need to implement this event in your code.) ）
do not create a second panel that is narrower than the main panel. If the main panel is narrower than the second panel, the column view controller can no longer fill the width of the screen and the overall appearance is unbalanced.
do not display the navigation bar in two panels at the same time. Doing so will make it very difficult for users to identify the relationship of two panels.
In General, the currently selected entries in the main panel are indicated in a persistent manner. Even if the contents of the second panel can be changed, it should always remain relevant to the entry selected in the main panel. This viewing experience will help people understand the relationship between the main panel entry and the second panel content.
If appropriate, give people an alternative way to get the main panel. By default, only the second panel is displayed in a horizontal compact environment, and you provide the user with a button (typically placed in the navigation bar) to display and hide the main panel. The Finnish view controller also supports swipe gestures to perform show/hide operations. Unless your app uses swipe gestures to perform other functions, you should let people swipe to get the main panel.
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"--split View Controller
