1 <?xml version="1.0" encoding="utf-8"?>

     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->

     3 <!-- This component and the accompanying materials are made available under the terms of the License 

     4 "Eclipse Public License v1.0" which accompanies this distribution, 

     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->

     6 <!-- Initial Contributors:

     7     Nokia Corporation - initial contribution.

     8 Contributors: 

     9 -->

    10 <!DOCTYPE concept

    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">

    12 <concept id="GUID-B8C3E562-EE45-47F2-BC00-F6C10ADD3026" xml:lang="en"><title>Definitions</title><prolog><metadata><keywords/></metadata></prolog><conbody><table id="GUID-4D35808B-97EE-4D2F-87FC-17480BFAC0FC">

    13 <tgroup cols="2"><colspec colname="col1"/><colspec colname="col2"/>

    14 <tbody>

    15 <row>

    16 <entry>Area registry based feedback</entry>

    17 <entry>Feedback is triggered by centralized registry, which is hosted by the

    18 feedback system. When some area with defined feedback is touched, the feedback

    19 is triggered by the system before any application even receives the pointer

    20 event. <p/>For this kind of feedback it is on application’s responsibility

    21 to add, update and remove areas to the registry according to application state.<p/> Area

    22 registry’s main purpose is to minimize the feedback latency by processing

    23 the pointer event faster than what would be possible from a normal GUI application.</entry>

    24 </row>

    25 <row>

    26 <entry>Direct feedback</entry>

    27 <entry>Feedback is triggered directly from the application, which receives

    28 the pointer event.</entry>

    29 </row>

    30 <row>

    31 <entry>Feedback latency</entry>

    32 <entry>The time that it takes from the moment when user touches the screen,

    33 until feedback is generated. This includes all the processing in touch driver

    34 and window server, as well as the time that it takes for actually starting

    35 the feedback.</entry>

    36 </row>

    37 <row>

    38 <entry>Logical feedback type</entry>

    39 <entry>Defines the nature of the feedback effect (e.g. “basic” or “sensitive”),

    40 but does not tell which type of physical feedback effect (vibrator pulse,

    41 sound effect etc.) is produced. Logical feedback type is decided by the UI

    42 component or application, which is using Tactile Feedback Client API for producing

    43 feedback. </entry>

    44 </row>

    45 </tbody>

    46 </tgroup>

    47 </table></conbody></concept>