You can certainly write an IME that does it. The SoftKeyboard sample code shows you where you would typically implement the UI part of it.
On Mon, Dec 22, 2008 at 12:28 AM, Yong <[email protected]> wrote: > > Hi Dianne Hackborn, > > Is IME & IMF going to support word prediction based on some language > dictionary? I find that features including dictionary of suggestions > and a suggestion algorithm are included in the IME roadmap for 2009 Q1 > release, and in the SoftKeyboard.java there is an commented line // > startPrediction(). > > Thanks. > > On Dec 20, 7:11 am, "Dianne Hackborn" <[email protected]> wrote: > > It is something after 1.0, but there is no release number assigned to it > > yet. That is why we use names instead of, when starting work, trying to > > predict the future and assign a release number. That rarely works out. > :) > > However, it certainly will not be a 1.0_rXXX version, since cupcake is > > changes to the platform which will result in something that is not 1.0. > > > > If an app tries to use one of the new APIs on a phone that is running an > > older version, best case it won't do anything, worst case the app will > not > > work at all. It depends on what you are doing. For example, using new > XML > > attributes will just be ignored on previous versions. Directly using > Java > > APIs will cause your app to break on previous versions because they don't > > exist there. You can use reflection to look to see if the API exists and > > call it indirectly if running on a version that has it. > > > > Right now cupcake is mostly in a state for platform engineers to work > with > > it. As we get closer to finishing on it, will we be putting together new > > SDKs that people can use to write apps against the new APIs. I think you > > might be able to build your own private SDK using the cupcake branch, but > we > > are not yet at the point where the APIs are stabilized so using them will > be > > a moving target (much like all of the pre-cupcake APIs were until we got > to > > 1.0). > > > > On Fri, Dec 19, 2008 at 2:49 PM, Ed Burnette <[email protected]> > wrote: > > > > > Pardon me if this has been answered before, but is the "cupcake" work > > > ultimately going into Android SDK version 2.0 or 1.1 or > > > 1.0_r<something>, and what happens when you run an app that uses a new > > > API like Window.setSoftInputMode() on a phone with the current Android > > > 1.0? > > > > > I'm wondering about the compatibility story in general so any light > > > you can shed on that would be appreciated. > > > > -- > > Dianne Hackborn > > Android framework engineer > > [email protected] > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support. All such questions should be posted on public > > forums, where I and others can see and answer them. > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
