Changes

Jump to: navigation, search

Using Xcode Storyboarding (iPhone iOS 5)

819 bytes removed, 14:07, 30 January 2012
no edit summary
<table border="0" cellspacing="0" width="100%">
<tr>
<td width="20%">[[Creating a Navigation based iOS 5 iPhone Application using TableViews|Previous]]<td align="center">[[iPhone iOS 5 Development Essentials|Table of Contents]]<td width="20%" align="right">[[Implementing a Page based Using Xcode Storyboards to create an iOS 5 iPhone Tab Bar Application using UIPageViewController|Next]]</td>
<tr>
<td width="20%">Creating a Navigation based iOS 5 iPhone Application using TableViews<td align="center"><td width="20%" align="right">Implementing a Page based Using Xcode Storyboards to create an iOS 5 iPhone Tab Bar Application using UIPageViewController</td>
</table>
<hr>
<google>BUY_IOS5</google>
 
 
The preceding chapter looked at manually coding screen navigation functionality into an iOS 5 iPhone application. The example presented in that chapter provides the flexibility that is generally required when implementing a master-detail based user interface comprising of a number of table view based screens. In practice, there are many situations where much simpler forms of navigation are required and where the coding work required for table view based navigation might well be considered overly complex. In recognition of this fact, Apple has introduced the concept of Storyboarding in Xcode 4.2.
 
The goal of this chapter is to provide an overview of storyboarding and to work through an example demonstrating this new Xcode feature in action.
 
== An Overview of Xcode Storyboarding ==
Storyboarding is a feature built into Xcode version 4.2 and later that allows both the various screens that comprise an iOS application and the navigation path through those screens to be visually assembled. Using the Interface Builder component of Xcode the developer simply drags and drops view controllers onto a canvas and designs the user interface of each view in the normal manner. The developer then drags lines to link individual trigger controls (such as a button) to the corresponding view controllers that are to be displayed when the control is selected by the user. Having designed both the screens (referred to the in the context of storyboarding as scenes) and specified the transitions between scenes (referred to as segues) Xcode generates all the code necessary to implement the defined behavior in the completed application. The style of transition for each segue (page fold, cross dissolve etc) may also be defined within Interface Builder. Further, segues may also be triggered programmatically in situations where behavior cannot be defined graphically using Interface Builder.
<table border="0" cellspacing="0" width="100%">
<tr>
<td width="20%">[[Creating a Navigation based iOS 5 iPhone Application using TableViews|Previous]]<td align="center">[[iPhone iOS 5 Development Essentials|Table of Contents]]<td width="20%" align="right">[[Implementing a Page based 16. Using Xcode Storyboards to create an iOS 5 iPhone Tab Bar Application using UIPageViewController|Next]]</td>
<tr>
<td width="20%">Creating a Navigation based iOS 5 iPhone Application using TableViews<td align="center"><td width="20%" align="right">Implementing a Page based 16. Using Xcode Storyboards to create an iOS 5 iPhone Tab Bar Application using UIPageViewController</td>
</table>

Navigation menu