[MeeGo-touch-dev] Help: How to implement a Input Method in IMF?
tornadory at 163.com
Tue Sep 7 19:30:56 PDT 2010
Thanks a lot, you make me more clear about the framework.
At 2010-09-07 21:14:21，"Pekka Vuorela" <pekka.ta.vuorela at nokia.com> wrote:
>On Tue, 2010-09-07 at 14:28 +0200, ext danny wrote:
>> I am ashamed that I could not confirm which way is the right way to
>> implement a Input Method in the IMF of MeeGo for handset after a long
>> time study.
>> Now I see there are some methods:
>> 1) Just like the VKB plugin, implements the MInputMethodPlugin and
>> MInputMethodBase, I thought this is a way to implement a Input Methods
>> engines manager and manage some real engines? is it right? Or
>> implement a real input method engine by this way?
>> [In this way, could I use the VKB exist? How could they communicate
>> with the server and each other if it is a right way to do?]
>Implementing an MInputMethodPlugin and a corresponding MInputMethodBase
>is the way to make a new plugin for the input method server to be used.
>These plugins will take care of painting whatever they need on the
>screen and/or handling hardware input on the hardware keyboard mode. The
>actual used plugin is then configured with gconf, e.g.:
> onscreen = MeegoKeyboard
> hardware = MeegoKeyboard
Does this mean that we could use only one plugin for onscreen or hardware, and if we implement a plugin like the VKB, and then we should set it in the gconf to make it used. So the original VKB plugin will be replaced and we should reimplement a VKB.
>> 2) Just like the dummy driver in the meegotouch-inputmethodengine
>> package, implement a real input method engine. is it right?
>> [In this way, how could I change the input methods engine when there
>> are more than one if it is a right way to do?]
>This is optional. If you want to use the input method engine interface
>for getting word corrections/predictions then by all means, but you can
>as well implement the functionality inside the input method plugin. Or
>you can just implement a plugin of this kind and make e.g. meego virtual
>keyboard use it for word corrections by setting a gconf value.
It seems that make a similar plugin and make it be used by the VKB is a better way, do you plan to use this way to support the CJK input?
And how could make this plugin be used by the VKB plugin? The plugin for input method is different from the VKB plugin and where it be put? also /usr/lib/meego-im-plugins or any others?
I am puzzled about the relationship between this kind of plugin and the VKB plugin.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MeeGo-touch-dev