summaryrefslogtreecommitdiffstats
path: root/doc/ApplicationGuide.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/ApplicationGuide.md')
-rw-r--r--doc/ApplicationGuide.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/ApplicationGuide.md b/doc/ApplicationGuide.md
index ae6ab0a..28b22b8 100644
--- a/doc/ApplicationGuide.md
+++ b/doc/ApplicationGuide.md
@@ -1,4 +1,4 @@
-# **Window Manager Application Guide**
+# Window Manager Application Guide
## Table of content
@@ -57,7 +57,7 @@ and projects before using Window manager.
# Overview
-Window Manager is the service process which provides **window management based on policy**.
+Window Manager is the service process which provides window management based on policy.
And implements a layout switching of applications on
multiple layers and with different layer layouts.
Window Manager is based on ivi layer management from GENIVI and AGL application framework.
@@ -79,12 +79,12 @@ In this example, there are two mode for window management.
The important points are:
-- **Window transition should be done by Window Manager**
+- Window transition should be done by Window Manager
Window Manager switch application displayed on top layer by user operation(touch shortcut button).
In this example, when an user touches `navigation` shortcut button, Window Manager displays `navigation` and hide `launcher`. Next, when an user touches `videoplayer` shortcut button, Window Manager divides a screen into two parts and display two applications.
-- **There is a priority `role` for each application.**
+- There is a priority `role` for each application.
Window Manager realizes state transition change based on the policy which consists of `role`.
According to the state transition table, it controls the visibility of application window, layout change, and so on.