轉換到 StoryBoard 的公佈說明（Converting to Storyboards Release Notes）

轉換到 StoryBoard 的公佈說明（Converting to Storyboards Release Notes）

太陽火神的漂亮人生 (http://blog.csdn.net/opengl_es)

本文遵循「署名-非商業用途-保持一致」創做公用協議

轉載請保留此句：太陽火神的漂亮人生 -  本博客專一於 敏捷開發及移動和物聯設備研究：iOS、Android、Html五、Arduino、pcDuino，不然，出自本博客的文章拒絕轉載或再轉載，謝謝合做。

轉換到 StoryBoard 的公佈說明（Converting to Storyboards Release Notes）

Storyboarding 是一種新的方式用於建立 iOS 應用的用戶界面。從 iOS 5 和 Xcode 4.2 開始引入。使用 storyboard，你可以把組成你的應用的視圖控制器設計成 Xcode 設計畫布中的場景。並且使用 segue 在場景間可視化地定義導航。

Storyboarding is a new way to create user interfaces for iOS applications, beginning with iOS 5 and Xcode 4.2. Using storyboards, you can design the view controllers that compose your application as scenes in the Xcode design canvas and visually define the navigation between the scenes using segues.

把一個已有的 iOS 應用轉換成使用 storyboard 需要採取一些步驟。另外。有一些其餘模式可以採用。

There are a few steps you need to take to convert an existing iOS application project to use storyboards. In addition, there are other new patterns you can adopt.

內容例如如下：

Contents:

• 配置應用代理
  Configure the Application Delegate
• 加入 Storyboard 到project
  Add a Storyboard to the Project
• 爲project設置主 Storyboard
  Set the Main Storyboard for the Project
• 訪問第一個視圖控制器
  Accessing the First View Controller
• 配置表視圖
  Configuring Table Views

配置應用代理
Configure the Application Delegate

應用代理負責載入 storyboard 並管理窗體。你需要在 UIApplicationMain 中指定應用代理類的名稱，並確保應用代理有一個叫 window 的屬性。

The application delegate is responsible for loading the storyboard and managing the window. You need to specify the name of the application delegate class in UIApplicationMain, and ensure that the application delegate has a property called window.

假設你沒有應用代理類，那麼需要建立一個。一個最小實現會像這樣：

If you don’t have an existing application delegate class, you need to create one. A minimal implementation would look like this:

Listing 1-1 最小應用代理頭文件 
Listing 1-1 Minimal application delegate header file

#import <UIKit/UIKit.h>

@interface AppDelegate : NSObject <UIApplicationDelegate>

@property (strong, nonatomic) UIWindow *window;

@end

Listing 1-2 最小應用代理實現文件
Listing 1-2  Minimal application delegate implementation file

#import "AppDelegate.h"

@implementation AppDelegate

@synthesize window = _window;

@end

注意: 在當前的 Xcode 模板中，應用代理類繼承自 UIResponder.。

這樣應用代理實例可以參與到 響應鏈 (responder chain) 以便處理應用層動做。假設你已存在的應用中未使用這種模式，就沒有必須爲 storyboard 採納它。

Note: In the current Xcode templates, the application delegate class inherits from UIResponder. This is so that the delegate instance can participate in the responder chain and so handle application-level actions. If you haven’t made use of this pattern in an existing application, there’s no need to adopt it for storyboards.

在 main.m 文件裏 UIApplicationMain 類裏設置應用代理。

In the main.m file, set the application delegate class in UIApplicationMain.

已有的 main.m 文件可能看起來像是這樣：

Your existing main.m file probably looks something like this:

#import <UIKit/UIKit.h>

int main(int argc, char *argv[]) {

NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];

int retVal = UIApplicationMain(argc, argv, nil, nil);

[pool release];

return retVal;

}

把它改爲這樣：

Change it to look like this:

#import <UIKit/UIKit.h>

#import "AppDelegate.h"

int main(int argc, char *argv[]) {

@autoreleasepool {

return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class]));

}

}

(將 「AppDelegate」 替換爲你的應用代理類的名字).

(replace 「AppDelegate」 with the name of your application delegate class).

注意: @autoreleasepool 是一個新的 Objective-C 語句用於管理本身主動釋放池；它可用於所有 Objective-C 模式。並且比使用 NSAutoReleasePool 類更高效（參看 遷移到 ARC 的公佈說明（Transitioning to ARC Release Notes））。

Note: @autoreleasepool is a new Objective-C statement for managing autorelease pools; it is available in all Objective-C modes, and is more efficient than using the NSAutoReleasePool class (see Transitioning to ARC Release Notes).

加入 Storyboard 到project中
Add a Storyboard to the Project

加入一個新的 storyboard 到project中。

按慣例，初始 storyboard 命名爲 MainStoryboard 。

Add a new storyboard file to the project. By convention, the initial storyboard is named MainStoryboard.

從對象庫中加入第一個視圖控制器到 storyboard。你應該會看一個無源的 segue。它指示這是第一個場景。

Add your first view controller to the storyboard from the Object library. You should see a sourceless segue indicating that this is the first scene.

假設第一個視圖控制器嵌入在諸如導航控制器或分頁控制器這種容器中，那麼使用 Editor > Embed In 來正確地嵌入它。

無源 segue 現在應該指向容器視圖控制器了。

If the first view controller is embedded in a container such as a navigation controller or tab bar controller, then use Editor > Embed In to embed it appropriately. The sourceless segue should now point to the container view controller:

爲項目設置主 Storyboard
Set the Main Storyboard for the Project

In the Summary for application Target, set the value of the Main Storyboard to the name of the storyboard file you created. If there is a value for Main Interface (to specify the first nib file), make sure you remove it.

訪問第一個視圖控制器
Accessing the First View Controller

The application delegate is not represented in the storyboard. If you need to access the first view controller (for example, if you are creating a Core Data application and want to pass the delegate’s managed object context to the first view controller), you can do so via the window’s rootViewController. If the root view controller is a container controller—such as an instance of UINavigationController—then you can access your view controller using the appropriate accessor for the container’s contents, for example:

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {

UINavigationController *rootNavigationController = (UINavigationController *)self.window.rootViewController;

MyViewController *myViewController = (MyViewController *)[rootNavigationController topViewController];

// Configure myViewController.

return YES;

}

配置表視圖
Configuring Table Views

There are several new ways of working with table views when you use storyboards.

• The dequeueReusableCellWithIdentifier: method is guaranteed to return a cell (provided that you have defined a cell with the given identifier). Thus there is no need to use the 「check the return value of the method」 pattern as was the case in the previous typical implementation of tableView:cellForRowAtIndexPath:. Instead of:

UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:CellIdentifier];

if (cell == nil) {

cell = [[UITableViewCell alloc] initWithStyle:UITableViewCellStyleDefault reuseIdentifier:CellIdentifier];

}

// Configure and return the cell.

• 
  
  you would now write just:

UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:CellIdentifier];

// Configure and return the cell.

• 
  
• You can configure table view cells directly in the table view. By default, the prototype cell style is set to Custom, so that you can design your own cell. You can also set the style to one of the built-in UITableViewCell cell styles by using the Attributes Inspector.  
• For a table view that is the view of a UITableViewController instance, you can configure static content directly in the storyboard. In the Attributes Inspector, set the content of the table view to Static Cells. 
  If you use static cells, you can connect outlets from the table view controller to individual cells so that you can configure the cell’s content at runtime.

// Declare properties for the outlets.

@property (nonatomic, weak) IBOutlet UITableViewCell *firstGroupFirstRowCell;

// Configure cells directly.

firstGroupFirstRowCell.detailTextLabel.text = newTextValue;

• 
  

Copyright © 2014 Apple Inc. All rights reserved. Terms of Use | Privacy Policy | Updated: 2011-10-12