From 60a0c199eb3e8819f7c47a2ada9092d78b29a06c Mon Sep 17 00:00:00 2001 From: Daiki Ueno Date: Tue, 22 Jun 2010 13:06:42 +0900 Subject: [PATCH] Fix doc. --- docs/reference/eek/eek-overview.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/eek/eek-overview.xml b/docs/reference/eek/eek-overview.xml index 462ff95b..81a1c8ed 100644 --- a/docs/reference/eek/eek-overview.xml +++ b/docs/reference/eek/eek-overview.xml @@ -52,12 +52,12 @@ clutter_group_add (CLUTTER_GROUP(stage), configuration directly (without libxklavier), you will only need to replace eek_xkl_layout_new () with eek_xkb_layout_new(). - To achieve the portability between different UI toolkits, + To achieve portability across different UI toolkits, there is a seperate represention of keyboard elements apart from the actual UI widgets. For example, a keyboard is represented as a tree of #EekElement -- #EekKeyboard contains one or more #EekSection's and - #EekSection contains one or more #EekKey's. Each element can relay - events when user taps on the UI widget. + #EekSection contains one or more #EekKey's. Each element may emit + events when user pushes the corresponding UI widget. Here is another sample code which demonstrates logical events on #EekElement: