Application states in MeeGo 1.2 Harmattan - Revision history

Hamishwillee: Text replace - "Category:MeeGo" to "Category:MeeGo Harmattan"

2012-06-13T10:51:23Z

Text replace - "Category:MeeGo" to "Category:MeeGo Harmattan"

SeemaB: SeemaB -

2011-10-03T17:07:25Z

SeemaB -

Croozeus: Croozeus - /* Application states */

2011-09-27T08:38:39Z

Croozeus - - Application states

Girishpadia: Girishpadia - /* Application states */

2011-09-25T03:41:46Z

Girishpadia - - Application states

SeemaB: SeemaB -

2011-09-24T20:09:45Z

SeemaB -

Girishpadia: Girishpadia -

2011-09-18T14:51:50Z

Girishpadia -

New page

[[Category:MeeGo]]
{{Abstract|This article explains the two states of an application in MeeGo 1.2 Harmattan}}

{{ArticleMetaData
|platform= MeeGo 1.2 Harmattan
|creationdate= 20110918
|author= [[User:girishpadia]]
}}

== 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.

{| class="wikitable"
|-
! Application State !! Description
|-
| Active State ||
# The application is running in the foreground.
# It can use more CPU and memory.
# 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 ||
# The application is running in the background.
# 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.
# 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 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'''.

For Example,

<code cpp>
if (platformWindow.active)
// do something
else
// do something
</code>

==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]

← Older revision		Revision as of 10:51, 13 June 2012
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}}

← Older revision		Revision as of 17:07, 3 October 2011
Line 38:		Line 38:


−	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,

@@ Line 14: / Line 14: @@
 ==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.
+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"
@@ Line 23: / Line 23: @@
 # The application is running in the foreground.
 # It can use more CPU and memory.
-# 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.
+# 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.
 |-

@@ Line 20: / Line 20: @@
 ! Application State !! Description
 |-
 | Active State ||
 # The application is running in the foreground.
 # It can use more CPU and memory.
 # 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 ||
 # The application is running in the background.
 # 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.
 # 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 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'''.
 For Example,
 <code cpp>
 if (platformWindow.active)
    // do something
 else
    // do something
 </code>
-−
 ==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]