|
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-57B7DA8C-A62F-4C65-B754-47D9F5E76416" xml:lang="en"><title>Text |
|
13 input</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
14 <p>There are several finger-optimized text input methods available for touch-enabled |
|
15 devices. The available methods depend on the orientation of the device. The |
|
16 following methods are available in the portrait orientation:</p> |
|
17 <ul> |
|
18 <li><p>Virtual ITU-T keyboard with text prediction</p></li> |
|
19 <li><p>Handwriting recognition (HWR) for some language variants. Not available |
|
20 for Latin languages.</p></li> |
|
21 </ul> |
|
22 <p>The following methods are available in the landscape orientation:</p> |
|
23 <ul> |
|
24 <li><p>Virtual QWERTY opened in full screen with input preview</p></li> |
|
25 <li><p>Handwriting recognition</p></li> |
|
26 </ul> |
|
27 <p>The input methods that are available to mobile device users depend on the |
|
28 product. Users can select the suitable input method for each situation from |
|
29 the input methods that are included in the product. The device recalls the |
|
30 last used method and offers it the next time when the user wants to input |
|
31 something.</p> |
|
32 <fig id="GUID-0A84FE47-C9D6-48AF-A4A5-F643342733F9"> |
|
33 <title>Virtual ITU-T keypad</title> |
|
34 <image href="GUID-F7A17E65-CB2D-41D3-9404-1A7D7F55FABC_d0e75876_href.png" placement="inline"/> |
|
35 </fig> |
|
36 <fig id="GUID-A294F7A7-79E4-41E3-8456-9554FA23A3B4"> |
|
37 <title>Virtual QWERTY keyboard</title> |
|
38 <image href="GUID-47AA7F26-FF3F-4FEE-BBB4-F4E8A8E0E335_d0e75884_href.png" placement="inline"/> |
|
39 </fig> |
|
40 <p>The virtual QWERTY keyboard displays a keyboard that has a collection of |
|
41 basic keyboard functions (Shift, Caps lock, punctuation marks, and so on) |
|
42 and a text field where the user can see the given input without having to |
|
43 follow it from the editor field. The handwriting recognition allows user to |
|
44 write characters on the screen with a finger.</p> |
|
45 <p>If touch input has been launched from an editor, pressing any hardware |
|
46 character key closes the touch input. This also applies to hybrid devices |
|
47 having both a hardware and virtual keyboard. Activating the hardware keyboard |
|
48 character key closes the virtual keyboard. Touch input never starts up automatically |
|
49 (that is, a change of view does not launch it), but the user has to launch |
|
50 it by tapping the editing field. Moving the focus onto an editing field with |
|
51 the hardware keys does not launch touch input.</p> |
|
52 <section id="GUID-122BA229-0C5D-47C7-ABDE-4C6279B79FFD"><title>Using |
|
53 touch-based text input in C++ applications</title><p>AVKON editor components |
|
54 support touch-based text input.</p><p>The API to use for providing touch-based |
|
55 text input is the <xref format="html" href="specs/guides/Editors_API_Specification/Editors_API_Specification.html" scope="peer">Editors API</xref>. For implementation information, see <xref format="html" href="specs/guides/Editors_API_Specification/Editors_API_Specification.html#Editors_API_Specification.topic3" scope="peer">Using the Editors API</xref>.</p></section> |
|
56 </conbody></concept> |