Using Barcode creation for iPhone Control to generate, create Code128 image in iPhone applications.

www.OnBarcode.com

The UIKit framework contains those classes most tightly connected to the iPhone, including all of the graphical classes you use to make up pages. A partial listing appears as table A.1. It s current as of iPhone OS 2.1, and will probably be mostly correct when you read this, but the UIKit does sometimes change between releases.

A listing of the most important User Interface classes (continued) Class Parent Summary An abstract class that is parent to many user controls A wheeled date-selection device A class that holds info about the iPhone itself A container for touches; part of the event model A font output class A non-displaying image holder

An image display that holds one or more UIImage objects A small, non-editable text display A hierarchical controller; often linked with a UITableViewController to produce hierarchical menus A toolbar for navigating among pages using dots A wheel-based selection mechanism A determinate progress display An abstract class that defines all classes that can receive and respond to events A class containing an iPhone s entire screen A parent class for views with multiple pages of content A text-input mechanism specialized for searches A control for making one of several choices A control for setting discrete values

UIPageControl UIPickerView UIProgressView UIResponder

UIControl UIView UIView NSObject

UIScreen UIScrollView UISearchBar UISegmentedControl UISlider

NSObject UIView UIView UIControl UIControl

Foundation framework classes

Table A.1 A listing of the most important User Interface classes (continued) Class Parent Summary A control for selecting binary values A controller for moving among multiple screens

A control for inputting short text A display for text of any size An individual touch on the iPhone s screen The abstract class that lies at the core of most UIKit objects A simple view controller A Safari-like web browser The root for the view hierarchy

Foundation framework classes

Foundation framework classes, whose names begin with NS, are almost as important as the UI classes because they represent foundational variable types, like strings and numbers. Table A.2 only lists the major classes that have some relevance to the sort of work you ve done in this book; for more, look at Apple s developer site under Core Services frameworks.

Table A.2 A listing of the most important Foundation classes Class Parent Summary An array A memory-management class A pointer toward a project s file system home Methods for managing characters An unordered collection of elements A wrapper for a byte buffer An associative array Encapsulated error information

A listing of the most important Foundation classes (continued) Class Parent Summary A methodology for controlling files A manager for file system work A node path A very important object for debugging; logs a formatted string to the system log An array that can be changed A character set that can be changed Data that can be changed A dictionary that can be changed A set that can be changed A string that can be changed A URL request that can be changed A notification manager A way to encapsulate many types of numbers The root class for Cocoa Touch A class for various sorts of string storage and manipulation A simple URL object A URL plus a cache policy A simple container for data An XML parser

The UI and NS classes should contain most of the objects you use when programming. We ve also covered several other frameworks throughout this book, including the Address Book framework (chapter 16), the Address Book UI framework (chapter 16), the Core Location framework (chapter 17), the Core Audio framework (chapter 18), the Media Player framework (chapter 18), the Core Graphics framework (chapters 18 and 19), the Quartz Core framework (chapter 19), the OpenGL ES framework (chapter 19), and the CFNetwork framework (chapter 20). Finally, you may wish to pay some attention to the Core Foundation framework, which we ve used (as infrequently as possible) throughout part 4 of this book.