Iphone Applications
Since each iPhone application is made under the UIKit, they are all fundamentally the same basic architecture. UIKit provides a solid basis on which not only the main objects to make the request, but also the need for user intervention to coordinate and control the information display on the screen. Therefore, applications do not show their individuality through their Core architecture, but in how they are configured as objects. In addition, diversity in iPhone applications are found in the use of custom objects to customize the application interface AOS and subsequent behavior.
Some changes to your application that is in your own code, many changes do occur at the highest level of demand. Whether in the default application to close the application or adaptation to the election will have an impact on how your application interacts with the system and other applications that are stored on the device. The developers have a basic knowledge of the architecture of the main application.
iPhone Core architecture
The vast majority of applications, SOA-key infrastructure, from beginning to end, will be controlled under UIKit. iPhone applications are always events and react to events in the system. The purpose of the application user interface manages the host aspect of this process, while the reaction to these events, the work of your custom code. Understanding the life cycle of events and an iPhone application lets you know when responding to events.
The life cycle
The lifecycle of an application is the sequence of events that occur between the beginning and the output of your application. In other words, iPhone applications will be launched when a user touches the icon on the home screen. Some images are transitional arrangement will appear to your application by clicking on all the main features. But after that date, the majority of the initialization UIKit successful loading of the application, and preparing the AOS user interface event loop. Then UIKit coordinate the transfer of events that your custom objects and responds to commands from the application. Finally, the user decides to terminate the application, the UIKit communicate this information and begins the process of termination. At the beginning and communicates UIKit end transfer with the application, inform what happens. In the case loops, dispatches information UIKit your event handler for individual applications.
The main function
While other applications depends on the task, not an iPhone applications. Instead, most of the work that an application to undertake the responsibility of the UI application main function. In fact, the main feature is three goals: it creates a pool self-liberation, communicates with the main application user interface, and releases the auto-release pool. Changing the implementation of this feature is not recommended. The application UI uses four main parameters for an application to start and should never change these defaults.
Delegate Application
The delegate object, you can check the behavior of high-level of your application. This element is a mechanism for sub-classification of objects to avoid UIKit complex. Technical Thus, instead of sub-classification or riding, the complex is unchanged, and set your custom code to be transferred. As events unfold, the complex transfer of information on the object communicates with your facility and the brackets used to run custom code.
Since the transfer application processes messages critical of the system should be included in an iPhone application. In addition, if the object, the application delegate protocol of the user interface that is used an example of a class.
The Main Nib File
During initialization, load your application’s main nib file aos. Although spring-file is the only file that automatically loads the nib more are added later. Being the source files are nib files on the hard drive and store a list of one or more objects. In a file mainspring for iPhone applications, you see that normally Recent modificationes Window object, the application property and other important objects, managing the window. When a spring file, the objects are restored and converted the drive to a memory representation in the edition that is handled by your application. NIB items using the downloaded files are the same as objects that are created programmatically.
Event management
After initialization, the structure of the main blocks of application loads the UI, which manage the application, OSA events and signs. The operating system recognizes the iPhone touch events and organizes them into the SOA application event queue as a user interaction with the device. Event management is organized so that the events of the subject application UI on the front of the queue is selected and restores to be most appropriate. Also events in the objects supplied controller is responsible for touching other events. For multi-touch events, the data in a case known as an event interface object.
As you can see, the iPhone applications behave a little differently than the traditional mobile web. With the touch panel of the device developers greater flexibility and control in their applications need, but with a basic knowledge of the basic architecture of iPhone applications will help you quickly adapt your programs for the ‘iPhone OS. Note that this section a very brief description of the architecture of iPhone applications, but you need a good idea of the processes underlying the iPhone applications.