Application states in MeeGo 1.2 Harmattan
(SeemaB -) |
hamishwillee
(Talk | contribs) m (Text replace - "Category:MeeGo" to "Category:MeeGo Harmattan") |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Category:MeeGo]] | + | [[Category:MeeGo Harmattan]] |
{{Abstract|This article explains the two states of an application in MeeGo 1.2 Harmattan}} | {{Abstract|This article explains the two states of an application in MeeGo 1.2 Harmattan}} | ||
| Line 14: | Line 14: | ||
==Application states== | ==Application states== | ||
| − | If your MeeGo 1.2 Harmattan (known as Harmattan in developer community) application is running, | + | If your MeeGo 1.2 Harmattan (known as Harmattan in developer community) application is running, it may be in the following two states. |
{| class="wikitable" | {| class="wikitable" | ||
| Line 20: | Line 20: | ||
! Application State !! Description | ! Application State !! Description | ||
|- | |- | ||
| − | | Active State || | + | | Active State || |
# The application is running in the foreground. | # The application is running in the foreground. | ||
| − | # It can use more CPU and memory. | + | # It can use more CPU and memory. |
| − | # In case, If an | + | # In case, If an active application uses more amount of memory and due to this, if all background applications have already been terminated, the out-of-memory situation can lead to the termination of the Active application. |
|- | |- | ||
| − | | Minimize State || | + | | Minimize State || |
# The application is running in the background. | # The application is running in the background. | ||
# The application should not perform any background processing, unless this was explicitly requested by the user. | # The application should not perform any background processing, unless this was explicitly requested by the user. | ||
# Applications must not update the UI when it is not visible to the end user. | # Applications must not update the UI when it is not visible to the end user. | ||
| + | # When applications detect a transition to the Minimized state they should free system resources to avoid being terminated by system in case of out of memory condition. | ||
# When applications are in the Minimized state, they can be closed in two different ways: | # When applications are in the Minimized state, they can be closed in two different ways: | ||
:* The end user closes the application from the task switcher UI. | :* The end user closes the application from the task switcher UI. | ||
:* The system terminates the application. This happens if the system runs out of memory available for applications. | :* The system terminates the application. This happens if the system runs out of memory available for applications. | ||
| − | |||
|} | |} | ||
| − | The change in the either of the state occurs by the user interaction. The application's state transition can be detected by '''platformWindow.windowState'''. | + | The change in the either of the state occurs by the user interaction. The application's state transition can be detected by '''platformWindow.windowState'''. |
| + | |||
| + | Following values can be retrieved from windowState: | ||
| + | :*windowState.visible | ||
| + | :*windowState.active | ||
| + | :*windowState.animating | ||
| + | :*windowState.viewMode | ||
| + | :*windowState.Fullsize | ||
| + | :*windowState.Thumbnail | ||
| + | :*windowState.viewModeString | ||
For Example, | For Example, | ||
<code cpp> | <code cpp> | ||
| − | if (platformWindow.active) | + | if (platformWindow.active) |
// do something | // do something | ||
else | else | ||
// do something | // do something | ||
</code> | </code> | ||
| − | + | ||
==More Information== | ==More Information== | ||
The more details can be obtained from [http://harmattan-dev.nokia.com/docs/library/html/guide/html/Developer_Library_Application_development_framework_Application_lifecycle.html here] | The more details can be obtained from [http://harmattan-dev.nokia.com/docs/library/html/guide/html/Developer_Library_Application_development_framework_Application_lifecycle.html here] | ||
Latest revision as of 13:51, 13 June 2012
This article explains the two states of an application in MeeGo 1.2 Harmattan
Article Metadata
Compatibility
Platform(s): MeeGo 1.2 Harmattan
Article
Created: girishpadia
(18 Sep 2011)
Last edited: hamishwillee
(13 Jun 2012)
Introduction
This article explains the two states of an application in MeeGo 1.2 Harmattan
Application states
If your MeeGo 1.2 Harmattan (known as Harmattan in developer community) application is running, it may be in the following two states.
| Application State | Description |
|---|---|
| Active State |
|
| Minimize State |
|
The change in the either of the state occurs by the user interaction. The application's state transition can be detected by platformWindow.windowState.
Following values can be retrieved from windowState:
- windowState.visible
- windowState.active
- windowState.animating
- windowState.viewMode
- windowState.Fullsize
- windowState.Thumbnail
- windowState.viewModeString
For Example,
if (platformWindow.active)
// do something
else
// do something
More Information
The more details can be obtained from here
