You are on page 1of 5

Configuring MPMS Application

Saving/Opening File Save the .zip file of source code on your mac machine. Open xcode, In the FILE navigator, select the OPEN. Now find you application(MPMS) code then find for 'MPMS.xcodeproj' file and click open xcode window will open.

Specifying the Targeted iOS Release You can take one of two strategies concerning the iOS release to target in developing your application: 1. Target the latest iOS release. Targeting the latest release allows you to take advantage of all the features available in the latest version of iOS. However, this approach may mean a smaller set of users capable of installing your application on their devices because your applications cannot run on iOS releases that are earlier than the target release. 2. Target an earlier iOS release. Targeting an earlier release lets you publish your application to a larger set of users (because your application runs on the target OS release and later releases). However, targeting an earlier release may limit the iOS features your application can use. To specify the earliest iOS release on which you want your application to run:

1. In the Project navigator, select the Edit Project Settings. 2. From the target list in the build tab, select the base SDK that builds your
application.

3. From the Deployment Target pop-up menu, choose the iOS release you want
to target. When you build your application, your deployment target selection is reflected in the MinimumOSVersion entry in the applications Info.plist file. When you publish your application to the App Store, the store indicates the iOS release on which your application can run based on the value of this property. Note: If the SDK youre using to build the application is more recent than the applications target iOS release (for example, the base SDK is iOS 4.3 and the deployment target is iOS 4.0), Xcode displays build warnings when it detects that your application is using a feature thats not available in the targeted iOS release. Important: When building for a simulator, the generated binary runs only on the iOS Simulator release thats part of the Xcode toolset release used to build the binary. It doesnt run on earlier or later releases of iOS Simulator.

Specifying the Targeted Architecture An iOS device uses one of a set of architectures, which include armv6 and armv7. The Architectures build setting identifies the architectures for which your application is built. You have two options for specifying the value of this setting:

Standard. Produces an application binary with a common architecture,


compatible with all supported iOS devices. This option generates the smallest application, but it may not be optimized to run at the best possible speed for all devices.

Optimized. Produces an application binary optimized for each supported iOS


device. However, the build time is longer than when using the Standard option, and the application is also larger because multiple instruction sets are bundled into it. To specify the earliest iOS architecture on which you want your application to run:

4. In the Project navigator, select the Edit Project Settings. 5. From the target list in the build tab, select the Architecture.
From the Deployment Architecture pop-up menu, choose the iOS architecture you want to target. If you need to build your application so that it contains executable code for a different set of architectures than these predefined values offer, you can choose Other from the Architecture build-setting value list and enter the desired iOS-device architecture names.

Setting Your Code Signing Identity (To Run application on your Device) When you build your application to run it on a device, Xcode signs it with a development certificate (also known as a code signing identity) stored on your keychain. The Code Signing Identity build setting specifies the provisioning profile and code signing identity Xcode uses to sign your binary. Xcode looks for code signing identities in your default keychain.

The possible values for the Code Signing Identity build setting are:

Dont Code Sign. Choose this option to build only for a simulator (also your by
default Signing Identity).

Automatic Profile Selector. Choose an option under this selector to select a


provisioning profile whose name starts with iPhone Developer or iPhone Distribution.

Specific Profile. Choose the code-signing identity under a specific provisioning


profile when your application requires special entitlements. Expired or otherwise invalid provisioning profiles are dimmed and cannot be used. Important: If you need to use different code signing identities that have the same name, you must use a separate Mac OS X user account for each identity.

Running Your Application : To run your application, choose Product > Run. Or You can use Build and Run/Debug icon on navigation bar of xcode. (if Breakpoints key shown in image is pressed then instead of Run there will be Debug icon)

When you run your application, Xcode places it in a simulation environment or on a device, and launches it. When your application runs on a device, you can ensure that it performs as you intend, using all the capabilities of your device. You should especially ensure that your application uses the devices resourcesCPU, memory, battery, and so onas efficiently as possible. Note: To run your application on a device, the device must be connected to your Mac through a USB cable.

Using iOS Simulator You use the iOS Simulator application to run your iOS application on your Mac. By simulating the operation of your application you: Learn about the Xcode development experience and the iOS development environment before becoming a member of the iOS Developer Program. Find major problems in your application during design and early testing. Test your applications user interface. Measure your applications memory usage before carrying out detailed performance analysis on iOS-based devices. The iOS Simulator application (located in <Xcode>/Platforms/iPhoneSimulator.platform/Developer/Applications) presents the iPhone or iPad user interface in a window on your computer. This application provides several ways of interacting with it by using your keyboard and mouse to simulate taps, device rotation, and other user actions. This chapter describes the ways in which you use your computers input devices to simulate the interaction between users and their devices. The chapter also describes how to uninstall applications from a simulator and how to reset the contents of a simulation environment.

Manipulating iOS- Simulator With iOS Simulator you can simulate most of the actions a user performs on a device. When your application is running in a simulator, you can carry out these hardware interactions through the Hardware menu:

Rotate Left. Rotates the simulator to the left. (+left navigation key) Rotate Right. Rotates the simulator to the right. (+right navigation key) Shake Gesture. Shakes the simulator. (^++Z) Home. Takes the simulator to the Home screen. (Shift++H) Lock. Locks the simulator. (+L) Toggle In-Call Status Bar. Toggles the status bar between its normal state
and its state when a phone call or FaceTime call is in progress. The status bar is taller in its in-call state than in its normal state. This command shows how your applications user interface looks when the user launches your application during a call.

Simulate Hardware Keyboard. Toggles the software keyboard on an an iPad


simulator. Turn off the software keyboard to simulate using a keyboard dock or wireless keyboard with an iPad device.

TV Out. Opens a window simulating the TV out signal of a device. Gesture (Pinch effects). For pinch effect you can use Alt/Option key of your
keyboard *Note : If you are using simple keyboard then instead of you can use Window key