What important Apple says about its split (iPad-Specific Controllers):
- A split view controller must always be the root of any interface you create.
- The panes of your split-view interface may then contain navigation controllers, tab bar controllers,…
- … the split view controller automatically handles most of the rotation behaviors
Everything is awesome except that we can’t use UISplitViewController inside TabBars. I’m sure there is a readon for that but sometime we need a bit more flexibility.
The main reason for custom UISplitViewController — it’s possible to be extended. For now:
- it always keeps both sides visible
- it’s always launched in the Portrait but rotated to any direction properly
- each side contains UINavigationController so it’s easy to do any navigation by pushing and poping UIViewControllers
- any number of APSplitViewController can be used inside tabs of UITabBarController (APCustomTabBarController included)
Future releases
Besides APSplitViewController is used in 3 real project it’s still in the initial stage. Functionality was gutted because it was necessary to get the component working well in a short time, and other such developments had sinned in those places that were critical to the projects. That’s why we’ve built this.
I want in future releases:
- launch with landscape mode (now it makes 20px shift)
- optionally hide left side in Portrait
- the divider to be drawn in CoreGraphics instead of PNG image
- optionally move divider in runtime
Fork APSplitViewController on Github
