The following is the first few sections of a chapter from The Busy Coder's Guide to Android Development, plus headings for the remaining major sections, to give you an idea about the content of the chapter.


The Input Method Framework

We think of Android devices as having “soft keyboards”. The official term for this is that Android devices offer one or more “input method editors” (or “input methods” for short). These input methods allow for text entry on a touchscreen, avoiding the need for a physical keyboard. Note, though, that “text entry” does not necessarily imply an on-screen keyboard equivalent — for example, the old PalmOS Graffiti text entry system is available as an app on the Play Store.

While it is possible to create custom input method editors — as the authors of Graffiti Pro did — this chapter is focused more on how ordinary app developers are affected by input methods, and how an app can help steer the behavior of the input method to benefit the user.

Prerequisites

Understanding this chapter requires that you have read the core chapters, particularly the section covering the EditText widget.

Keyboards, Hard and Soft

The preview of this section is being chased by zombies.

Tailored To Your Needs

The preview of this section is off trying to sweet-talk the Khaleesi into providing us with a dragon.

Tell Android Where It Can Go

The preview of this section was abducted by space aliens.

Fitting In

The preview of this section was abducted by space aliens.

Jane, Stop This Crazy Thing!

The preview of this section was eaten by a grue.