M.

Usman Khan 8th Semester UET Peshawar

Thursday, April 26, 12

Thursday, April 26, 12

Apple TV

iPhone

iPad

iPod Touch

Thursday, April 26, 12

Thursday, April 26, 12

Thursday, April 26, 12

Application Cocoa touch Media Layer Core Services Core OS

Thursday, April 26, 12

Application Cocoa touch Media Layer Core Services Core OS

Thursday, April 26, 12

Application Cocoa touch Media Layer Core Services Core OS

Thursday, April 26, 12

Application Cocoa touch Media Layer Core Services Core OS

Thursday, April 26, 12

Application Cocoa touch Media Layer Core Services Core OS

Core Frameworks

Thursday, April 26, 12

Cocoa Touch

Thursday, April 26, 12

Cocoa Touch

UIKit Cocoa touch

Thursday, April 26, 12

Cocoa Touch

UIKit Cocoa touch

Thursday, April 26, 12

Cocoa Touch

Thursday, April 26, 12

Cocoa Touch

Thursday, April 26, 12

Cocoa Touch

Thursday, April 26, 12

Cocoa Touch

Thursday, April 26, 12

Cocoa Touch

Thursday, April 26, 12

Cocoa Touch

Thursday, April 26, 12

Cocoa Touch

Graphical and Event-driven Apps.

Thursday, April 26, 12

Cocoa Touch

Graphical and Event-driven Apps. Builds on Mac OSX Framework but Optimized for Touch.

Thursday, April 26, 12

Cocoa Touch

Graphical and Event-driven Apps. Builds on Mac OSX Framework but Optimized for Touch. Implemented in Objective-C (C and C++).

Thursday, April 26, 12

Cocoa Touch

Graphical and Event-driven Apps. Builds on Mac OSX Framework but Optimized for Touch. Implemented in Objective-C (C and C++). Follows Model-View-Controller software architecture.

Thursday, April 26, 12

Cocoa Touch

Graphical and Event-driven Apps. Builds on Mac OSX Framework but Optimized for Touch. Implemented in Objective-C (C and C++). Follows Model-View-Controller software architecture. Powerful frameworks like Core Animation, Core Audio, Core Data.

Thursday, April 26, 12

Thursday, April 26, 12

Model-View-Controller

Thursday, April 26, 12

Model-View-Controller
1. 2. 3. 4. The user interacts with the user interface in some way (for example, pressing a button). The controller handles the input event from the user interface, and converts the event into an appropriate user action, understandable for the model. The controller noties the model of the user action, possibly resulting in a change in the model's state. A view queries the model to generate an appropriate user interface. The view gets its own data from the model. In some implementations, the controller may issue a general instruction to the view to render itself. In others, the view is automatically notied by the model of changes in state that require a screen update. The user interface waits for further user interactions, which restarts the control ow cycle.

5.

Thursday, April 26, 12

Model-View-Controller
1. 2. 3.

Controller

4.

5.

The user interacts with the user interface in some way (for example, pressing a button). The controller handles the input event from the user interface, and converts the event into an appropriate user action, understandable for the model. The controller noties the model of the user action, possibly resulting in a change in the model's state. A view queries the model to generate an appropriate user interface. The view gets its own data from the model. In some implementations, the controller may issue a general instruction to the view to render itself. In others, the view is automatically notied by the model of changes in state that require a screen update. The user interface waits for further user interactions, which restarts the control ow cycle.

View
Thursday, April 26, 12

Model

Model-View-Controller
1. 2. 3.

Controller

4.

5.

The user interacts with the user interface in some way (for example, pressing a button). The controller handles the input event from the user interface, and converts the event into an appropriate user action, understandable for the model. The controller noties the model of the user action, possibly resulting in a change in the model's state. A view queries the model to generate an appropriate user interface. The view gets its own data from the model. In some implementations, the controller may issue a general instruction to the view to render itself. In others, the view is automatically notied by the model of changes in state that require a screen update. The user interface waits for further user interactions, which restarts the control ow cycle.

View
Thursday, April 26, 12

Model

Model-View-Controller
1. 2. 3.

Controller

4.

5.

The user interacts with the user interface in some way (for example, pressing a button). The controller handles the input event from the user interface, and converts the event into an appropriate user action, understandable for the model. The controller noties the model of the user action, possibly resulting in a change in the model's state. A view queries the model to generate an appropriate user interface. The view gets its own data from the model. In some implementations, the controller may issue a general instruction to the view to render itself. In others, the view is automatically notied by the model of changes in state that require a screen update. The user interface waits for further user interactions, which restarts the control ow cycle.

View
Thursday, April 26, 12

Model

Model-View-Controller
1. 2. 3.

Controller

4.

5.

The user interacts with the user interface in some way (for example, pressing a button). The controller handles the input event from the user interface, and converts the event into an appropriate user action, understandable for the model. The controller noties the model of the user action, possibly resulting in a change in the model's state. A view queries the model to generate an appropriate user interface. The view gets its own data from the model. In some implementations, the controller may issue a general instruction to the view to render itself. In others, the view is automatically notied by the model of changes in state that require a screen update. The user interface waits for further user interactions, which restarts the control ow cycle.

View
Thursday, April 26, 12

Model

Model-View-Controller
1. 2. 3.

Controller

4.

5.

The user interacts with the user interface in some way (for example, pressing a button). The controller handles the input event from the user interface, and converts the event into an appropriate user action, understandable for the model. The controller noties the model of the user action, possibly resulting in a change in the model's state. A view queries the model to generate an appropriate user interface. The view gets its own data from the model. In some implementations, the controller may issue a general instruction to the view to render itself. In others, the view is automatically notied by the model of changes in state that require a screen update. The user interface waits for further user interactions, which restarts the control ow cycle.

View
Thursday, April 26, 12

Model

Core Services

Thursday, April 26, 12

Core Services

Foundation Frameworks Core Services

Thursday, April 26, 12

Core Services

Thursday, April 26, 12

Core Services

Thursday, April 26, 12

Core Services

Thursday, April 26, 12

Core Services

Thursday, April 26, 12

Core Services

Contains Fundamental System Services all Applications use. Services on top of which other layers are made. Accessed by the Cocoa touch layer. Core data framework, Core foundation framework, Core telephony framework, Core Location framework etc.

Thursday, April 26, 12

iOS SDK

Thursday, April 26, 12

Xcode

*Development on actual device requires signing up for Apple`s Paid iOS Developer Program and conguring the device for developmental purposes.
Thursday, April 26, 12

Xcode

Integrated Development Environment - Edit, compile, run and debug.

*Development on actual device requires signing up for Apple`s Paid iOS Developer Program and conguring the device for developmental purposes.
Thursday, April 26, 12

Xcode

Integrated Development Environment - Edit, compile, run and debug. Instruments - Runtime Performance Analysis & Debugging Tool.

*Development on actual device requires signing up for Apple`s Paid iOS Developer Program and conguring the device for developmental purposes.
Thursday, April 26, 12

Xcode

Integrated Development Environment - Edit, compile, run and debug. Instruments - Runtime Performance Analysis & Debugging Tool. Lets you run and debug directly on an attached device.*

*Development on actual device requires signing up for Apple`s Paid iOS Developer Program and conguring the device for developmental purposes.
Thursday, April 26, 12

Xcode

Integrated Development Environment - Edit, compile, run and debug. Instruments - Runtime Performance Analysis & Debugging Tool. Lets you run and debug directly on an attached device.* Supports C, C++, and Objective C.

*Development on actual device requires signing up for Apple`s Paid iOS Developer Program and conguring the device for developmental purposes.
Thursday, April 26, 12

Thursday, April 26, 12

Thursday, April 26, 12

Developmental Resources

Thursday, April 26, 12

Developmental Resources
Beginning iOS 5 Development By David Mark, Jack Nutting, Jeff LeMarche

Thursday, April 26, 12

Developmental Resources
Learn Objective-C on the Mac By Scott Knaster, Mark Dalrymple

Thursday, April 26, 12

Developmental Resources

iPad and iPhone App Development by Stanford

Thursday, April 26, 12

Developmental Resources

developer.apple.com

Thursday, April 26, 12

Developmental Resources

Thursday, April 26, 12

!ank Y"
Thursday, April 26, 12