From 1f23e74fa044b1d04d368c2d4093980ae553c0b2 Mon Sep 17 00:00:00 2001
From: sreevanis Wear 2.0 comes with the system default Input Method Editor (IME)
and opens up the IMF APIs for third-party developers to create custom input
-methods for Wear.
-

Figure 1. Sample input methods
The Android platform provides a standard framework for creating IMEs. To create + a wear-specific IME, you need to optimize your IME for limited screen size. +
-To create an input method for Wear, -see Creating an Input Method. +
This document provides guidance that can help you create a wear-specific IME. +Before you continue with this guide, it's important that you first read the +documentation for Creating an Input Method + on handsets.
-To control how your application is filtered from devices that do not support Wear @@ -64,9 +70,9 @@ IMEs (for example, on Phone), add the following to your application's manifest: can invoke your IME from:
{@code RemoteInput} and Wear apps expect only single-line text entry. The ENTER key should always trigger - a call to sendDefaultEditorAction, + a call to sendDefaultEditorAction, which causes the app to dismiss the keyboard and continue on to the next step or action.
-Most on-screen input methods will consume most of the screen, leaving very little - of the app visible; hence, we discourage Android Wear apps from presenting a - visible {@code EditTextView}. Instead, a full-screen IME uses - ExtractEditText - to render its own view of the attached editor, also providing control over the - styling of this view. You can ignore all editor-related events that the IME - doesn't generate. -For more details on full-screen mode, see -InputMethodService. +Input methods on Wear will consume most of the screen, leaving very little of the + app visible; Using full-screen mode ensures an optimal user experience regardless + of the application UI. In full screen mode, an + {@code ExtractEditText} provides a mirrored + view of the text field being edited and can be styled to blend with the rest of + the input method UI. For more details on full-screen mode, see + InputMethodService.
-For privacy reasons, at a minimum you should handle the {@code inputType} +For privacy reasons, at a minimum you should handle the {@code InputType} flag {@code TYPE_TEXT_VARIATION_PASSWORD} in your IME. When your IME is in password mode, make sure that your keyboard is optimized for single key press (auto spelling correction, auto completion and gesture input are disabled). Most importantly, keyboard in password mode should support ASCII symbols regardless of the input language. For more details, see -Specifying The Input Method Type. +Specifying The Input Method Type.
Android allows users to easily switch between all IMEs supported by the platform. In your IME implementation, set the boolean - supportsSwitchingToNextInputMethod = true + supportsSwitchingToNextInputMethod = true to enable your IME to support switching mechanism (so that apps can switch to the next platform-supported IME).
@@ -124,13 +128,5 @@ Android allows users to easily switch between all IMEs supported by the platform -To test your IME, install the
-Input Box
- app which has a simple EditText field.
- When responding to messages from chat apps, you can also use the IME on the
- watch.
&aT=uA21WX9*=W?* $Q$Hbj_lw+C}0VPn}JA|ENXAO(B2DT<-#sOXK
zu1Jv4)pX~0htqQe@{M}|X@{W}UTux}fd}ey#meUmg?`x3G47`vl3AtID?|3tx&JQ4
zV8vu{%gf|wZD`xBCg&&)I4+l1evQZ*&vx!LCt#AnU>-`=J@Jx~Bl?IC?^djY^|6^v
z -aqE$xGAL8euTO4+&3TIuYedlL6Dv;G_(piCkr
zCbt}HDC3)7xSS(08QAf%$YChA0|er~RA#gJ^1&!w8c}DmZxDbkGCGOU>Say%MBL>|
z$i~#n4x^B3LxwHeB;aM*Ky%+v3@kMU*XEHDJ5t9A^($P{dz&DbcEP5Fy5xTjn&J}U
z9PsE5d3qqD=S?4Fsc~&fPEp&P5OtKQ;#Xk{c{tj(PDf 8B_X+0Y4(#tAf+YZN6|Bm1>tolRN5;+?pC3ChwRh;}!fHNS8zkzwvyyn~W%NC&$2C(@qD|R6-gqL^
zQjSuPzcUTK7JM4omzXepxqX#q$pFvsnFJp@%F8QYs9}kE!_0vyVq&!!KY4gzl$~t$
z=b>r$SdIdf
7e5h0Uc#|D20cfhuX*Rl+!g0TIJ`iKONQdH=;>(tTMNZmJowKv+k