iOS开发入门指南：技术概览与关键框架

需积分: 5 65 浏览量更新于2024-07-16 收藏 3.59MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

资源详情

资源推荐

Storyboards

Introduced in iOS 5, storyboards supplant nib files as the recommended way to design your application’s user

interface. Unlike nib files, storyboards let you design your entire user interface in one place so you can see all

of your views and view controllers and how they work together. An important part of storyboards is the ability

to define segues, which are transitions from one view controller to another. Applications can define these

transitions visually in Xcode or initiate them programmatically in Xcode. These transitions allow you to capture

the flow of your user interface in addition to the content.

You can use a single storyboard file to store all of your application’s view controllers and views, or you can use

multiple view storyboards to organize portions of your interface. At build time, Xcode takes the contents of

the storyboard file and divides it up into discrete pieces that can be loaded individually for better performance.

Your application never needs to manipulate these pieces directly, though. The UIKit framework provides

convenience classes for accessing the contents of a storyboard from your code.

For more information about using storyboards to design your interface, see Xcode 4 User Guide . For information

about how to access storyboards from your code, see the UIStoryboard Class Reference.

Document Support

Introduced in iOS 5, the UIKit framework introduced the UIDocument class for managing the data associated

with user documents. This class makes implementing documentbased applications much easier, especially

applications that store documents in iCloud. In addition to providing a container for all of your documentrelated

data, the UIDocument class provides builtin support for asynchronous reading and writing of file data, safe

saving of data, automatic saving of data, support for detecting iCloud conflicts, and support for flat file or

package file representations. For applications that use Core Data for their data model, you can use the

UIManagedDocument subclass to manage your data stores.

For information about using documents in your apps, see Document-Based App Programming Guide for iOS .

Multitasking

Applications built using iOS SDK 4.0 or later (and running in iOS 4.0 and later) are not terminated when the

user presses the Home button; instead, they shift to a background execution context. The multitasking support

defined by UIKit helps your application transition to and from the background state smoothly.

To preserve battery life, most applications are suspended by the system shortly after entering the background.

A suspended application remains in memory but does not execute any code. This behavior allows an application

to resume quickly when it is relaunched without consuming battery power in the meantime. However,

applications may be allowed to continue running in the background for the following reasons:

●

An application can request a finite amount of time to complete some important task.

Cocoa Touch Layer

HighLevel Features

●

An application can declare itself as supporting specific services that require regular background execution

time.

●

An application can use local notifications to generate user alerts at designated times, whether or not the

application is running.

Regardless of whether your application is suspended or continues running in the background, supporting

multitasking does require additional work on your part. The system notifies your application as it transitions

to and from the background. These notification points are your cue to perform any important application tasks

such as saving user data.

For more information on how to handle multitasking transitions, and for information on how to request

background execution time, see iOS App Programming Guide .

Printing

Introduced in iOS 4.2, the UIKit printing support allows applications to send content wirelessly to nearby

printers. For the most part, UIKit does all of the heavy lifting associated with printing. It manages the printing

interfaces, works with your application to render the printable content, and handles the scheduling and

execution of print jobs on the printer.

Print jobs submitted by your application are handed off to the printing system, which manages the actual

printing process. Print jobs from all applications on a device are queued and printed on a firstcome, firstserved

basis. Users can get the status of print jobs from the Print Center application and can even use that application

to cancel print jobs. All other aspects of printing are handled for you automatically by the system.

Note: Wireless printing is available only on devices that support multitasking. You can use the

UIPrintInteractionController object to detect whether printing is available to your application.

For information about how to incorporate printing support into your applications, see “Printing” in Drawing

and Printing Guide for iOS .

UI State Preservation

Introduced in iOS 6, state preservation makes it easier for apps to restore their user interface to the state it was

in when the user last used it. When an app moves to the background, it is asked to save the semantic state of

its views and view controllers. Upon relaunch, the app uses this state to restore its interface and make it seem

as if the app had never quit. Support for state preservation is integrated into UIKit, which provides the

infrastructure for saving and restoring your app’s interface.

Cocoa Touch Layer

HighLevel Features

For more information about how to add state preservation support to your app, see iOS App Programming

Guide .

Apple Push Notification Service

Introduced in iOS 3.0, the Apple Push Notification Service provides a way to alert users of new information,

even when your application is not actively running. Using this service, you can push text notifications, add a

badge to your application icon, or trigger audible alerts on user devices at any time. These messages let users

know that they should open your application to receive the related information.

From a design standpoint, there are two parts to making push notifications work for iOS applications. First,

the application must request the delivery of notifications and process the notification data once it is delivered.

Second, you need to provide a serverside process to generate the notifications in the first place. This process

lives on your own local server and works with Apple Push Notification Service to trigger the notifications.

For more information about how to configure your application to use remote notifications, see Local and Push

Notification Programming Guide .

Local Notifications

Introduced in iOS 4.0, local notifications complement the existing push notification mechanism by giving

applications an avenue for generating the notifications locally instead of relying on an external server.

Applications running in the background can use local notifications as a way to get a user’s attention when

important events happen. For example, a navigation application running in the background can use local

notifications to alert the user when it is time to make a turn. Applications can also schedule the delivery of

local notifications for a future date and time and have those notifications delivered even if the application is

not running.

The advantage of local notifications is that they are independent of your application. Once a notification is

scheduled, the system manages the delivery of it. Your application does not even have to be running when

the notification is delivered.

For more information about using local notifications, see Local and Push Notification Programming Guide .

Gesture Recognizers

Introduced in iOS 3.2, gesture recognizers are objects that you attach to views and use to detect common

types of gestures such as swipes and pinches. After attaching a gesture recognizer to your view, you tell it

what action to perform when the gesture occurs. The gesture recognizer object then tracks the raw touch

events and applies the systemdefined heuristics for what the given gesture should be. Without gesture

recognizers, you must do all this work yourself, which can be quite complicated.

Cocoa Touch Layer

HighLevel Features

剩余68页未读，继续阅读

weixin_42081591

粉丝: 0
资源: 1

iOS开发入门指南：技术概览与关键框架

iOS技术概述中文版.pdf

TDOA定位技术详解及其实现方法

matlab求数组长度《MD文档》

大学生职业生涯规划书Word模板范文就业求职简历应聘工作PPT物流专业

Python 实现GPR高斯过程回归多输入单输出回归预测（多指标评价）（包含详细的完整的程序和数据）

并行编程加速器：Fortran中的OpenMP深度解析《word文档》

2024嵌入式面试资料GCC中文手册2024嵌入式面试资料GCC中文手册

校园医疗保险管理系统 JAVA高分毕业设计 Vue.JS+SpringBoot前后端分离项目.zip

chan算法详细学习教程攻略 chan算法原理应用场景概述

嘿哟论坛社区小程序V1.1.3全开源解密版+小程序前端.zip

公共管理视域下的城市老旧小区改造设计.pdf

KMP算法算法的实现包括next数组的构建以及算法主体，并附上注释

暴风电视刷机 58X4 ECHO 屏V580DJ4-QE1 机编60000AM0F00 屏参30173201 V1.0.35版本

汉语言文学多元化对文学评论传统的影响研究.pdf

基于树莓派实现人脸识别门禁系统高分项目+源码.zip

636F3C56-3477-440D-9523-0023F7A769DE.pdf

新媒体视域下的汉语言文学发展路径.pdf

最新的点微同城36.7-修复版

最新资源