extending soft-keyboard with language switching support?

by Henrik » Fri, 23 Apr 2010 08:03:47 GMT


Sponsored Links
 I just got my HTC Desire with Android 2.1, and the first problem I'm
running into a lot is when using the visual keyboard.  Being
multilingual and having friends who only speak one particular
language, there's no single 'correct' input language setting for the
word prediction feature, so I started looking into how much work it
might be to extend the keyboard with two rather basic, though
essential, features:

1)  Showing the current language selection, so that I don't have to
type stuff, getting it mis-corrected, then discover the language
setting must be wrong, go into the settings, select to change
language, select language, etc... until I get back, erase the old text
and start over. That gets old real quick..

2)  Being able to simple change whatever language is used for the word
prediction by just having a button on the keyboard doing that
directly, i.e. a button that just cycles through the 'relevant'
languages with the key label showing which is currently active.

Improving it even further, one might imagine:

3)  Having a per contact setting, noting the word-prediction language
that should be used when communicating with that user.

But searching through the docs, I'm slowly coming to the realization
that the input text language setting may not even be available to be
changed outside the system settings dialog, making this impossible to
implement - is that correct?

Regards,
Henrik Gram

--



Other Threads

1. Better App Management

In my view, one of Android's biggest advantages above other platforms
are it's app capabilities.  Android gives developers tremendous power
to leverage contacts, maps, location, intents, broadcast receivers,
content providers and background/multi-tasking to create amazing apps
and a great, cohesive system.

This is a tremendous power, and without sounding too much like
Spiderman, with great power comes great responsibility.

When developers misuse this responsibility it hurts Android as a
whole, creating insecure situations, compromising data or just slowing
the system down and crashing.

The balance between use and misuse is very tricky (highlighted in
permissions, where users question what an app uses each permission
for).  Overall, while power to the developer is important, I would
suggest the following to put the power back in the user`s hand:

Overall, there needs to be better Application Management.  By this I
mean no just installing and uninstalling, but the ability to control
apps on a more granular level.  For example, some applications need to
run on start up, and that is a valuable feature.  However, some apps
misuse this feature and make the powering on of my device much slower
than need be.  I cannot think of a single example of when an app HAS
to start on boot (if it doesn`t start up, that`s that same as if it
was uninstalled!), so this app management feature should be able to
control which apps I allow to start on boot (task killers, location
trackers, etc) and which I do not allow (eg notepad apps).

Also, background processing is a huge feature (multitasking), but it
also is often abused.  The ability to specify the apps that are
allowed to run in the background (use CPU & resources), apps that only
persist state (stay in memory) and apps that are not allowed to
persist at all.  This would give tremendous power and overall improve
the Android landscape.

My two cents.

-- 

2. Latest Google App

Got to admit, it's improved life at home with my cats;

http://www.youtube.com/watch?v=3I24bSteJpw&feature=player_embedded

Al.
--

* Looking for Android Apps? - Try http://andappstore.com/ *

======
Funky Android Limited is registered in England & Wales with the company number  
6741909. 

The views expressed in this email are those of the author and not necessarily 
those of Funky Android Limited, it's associates, or it's subsidiaries.

-- 

3. How to generate "uImage" in stead of "zImage" when build Android kernel

4. Taking picture with Camera

5. SurfaceFlinger, Frame buffer device, Overlays

6. GsmCellLocation.getCid() returns very large numbers.

7. Playlist Content Provider