[immodule-qt] Does QT 4 beta 1 support IM modules

[Daisuke Kameda]

Lars Knoll <lars at trolltech.com> wrote:

> > As long as the argument was read, I have a feeling that such a function is
> > not what the toolkit should realize. I think that what it should implement
> > is mechanism which lap those functions that other frameworks implement.
> 
> There should be a mechanism for doing this that is independent of the toolkit. 
> However the toolkits have to implement support for this mechanism (once it 
> exists).

I also think so. I feel that the relation between XDND and Qt is ideal relation.


> > QMultiInputContext is never mere switcher.
> > QMultiInputContext which we implemented has the following roles.
> >
> >
> > 1. The input method which is able to delegate processing of events to the
> >    arbitrary input methods can be created by inheriting QMultiInputContext
> >    and using changeInputMethod(). This is one of the meanings of "Multi."
> >
> >    For example, IM can be more easily created by leaving
> > QSimpleInputContext except the state where isComposing() is true.
> 
> I don't think I understand you here.

Sorry, I explain using other example.

Please assume the situation of wanting to make input method for using Japanese 
and the language other than English. In this case, if it is implemented as 
follows, it is realizable immediately. Only when a Japanese input is active, 
Japanese input method (Anthy, canna, etc.) is used, and when other, input method 
to which m17n-lib corresponds is used.

This is easily realizable if QMultiInputContext is used. The QInputContext class 
which inherited QMultiInputContext is only implemented, to which only when a 
specific key (for example, Zenkaku_Hankaku) is pushed Japanese input method 
operates, and in other, input method to which m17 n-lib corresponds operates. 

Although I do not know since I am not a specialist, probably there will be uses 
various otherwise.


> > 2. In the present implementation, using default IM other than XIM can be
> >    realized, only when QMultiInputContext is added. The great portion of
> >    meaning which adopt the result of an immodule for Qt project will be
> > lost, if it is still this state.
> 
> No. You can directly configure Qt to use some other IM plugin. That said, we 
> should have a switching framework available in Qt.

Have you said the general-purpose framework?
In present situation, the function to set up defaut IM and changing using 
context menu is enough for Qt. Moreover, if much function are required, 
we will be troubled by later.


> > 3. Switching input method by selecting context menu.
> 
> We will add this again in Qt.


-- 
Daisuke Kameda <kaminmat at cc.rim.or.jp>