![](https://csdnimg.cn/release/download_crawler_static/4963768/bgf.jpg)
■ Popovers layer content temporarily on top of your existing views. You can use them to implement tool
palettes, options menus, and present other kinds of information without distracting the user from the
main content of your application.
■ Modally presented controllers now support a configurable presentation style, which determines whether
all or only part of the window is covered by the modal view.
■ Toolbars can now be positioned at the top and bottom of a view. The increased screen size also makes
it possible to include more items on a toolbar.
■ Responder objects now support custom input views. A custom input view is a view that slides up from
the bottom of the screen when the object becomes the first responder. Previously, only text fields and
text views supported an input view (the keyboard) and that view was not changeable. Now, you can
associate an input view with any custom views you create. For information about specifying a custom
input view, see “Input Views and Input Accessory Views” (page 77).
■ Responders can also have a custom input accessory view. An input accessory view attaches itself to the
top of a responder’s input view and slides in with the input view when the object becomes first responder.
The most common use for this feature is to attach custom toolbars or other views to the top of the
keyboard. For information about specifying a custom input accessory view, see “Input Views and Input
Accessory Views” (page 77).
As you think about the interface for your iPad application, consider incorporating the new elements whenever
appropriate. Several of these elements offer a more natural way to present your content. For example, split
views are often a good replacement (or supplement) to a navigation interface. Others allow you to take
advantage of new features and to extend the capabilities of your application.
For detailed information on how to use split views, popovers, and the new modal presentation styles, see
“Views and View Controllers” (page 37). For information on input views and input accessory views, see
“Custom Text Processing and Input” (page 77). For guidance on how to design your overall user interface,
see iPad Human Interface Guidelines.
Enhanced Support for Text Input and Display
In earlier versions of iPhone OS, text support was optimized for simple text entry and presentation. Now, the
larger screen of iPad makes more sophisticated text editing and presentation possible. In addition, the ability
to connect a physical keyboard to an iPad device enables more intense text entry. To support enhanced text
entry and presentation, iPhone OS 3.2 also includes several new features that you can use in your applications:
■ The Core Text framework provides support for sophisticated text rendering and layout.
■ The UIKit framework includes several enhancements to support text, including:
❏
New protocols that allow your own custom views to receive input from the system keyboard
❏
A new UITextChecker class to manage spell checking
❏
Support for adding custom commands to the editing menu that is managed by the
UIMenuController class
■ Core Animation now includes the CATextLayer class, which you can use to display text in a layer.
What’s New for iPad Devices? 15
2010-03-14 | © 2010 Apple Inc. All Rights Reserved.
CHAPTER 1
About iPad Development