[immodule-qt] Re: Question about svn trunk
Daisuke Kameda
kaminmat at cc.rim.or.jp
Thu Jul 15 20:07:23 EEST 2004
On Thursday 15 July 2004 01:19, LiuCougar wrote:
> > What do you think 'API for external IM-switching' as? I think that
> > no additional API is required to communicate with external
> > IM-switching infrastructure. The switcher may be able to be
> > implemented as ordinary IM plugin. Suppose SCIM. Although it
> > only switches between its own IMEngines, all input methods are
> > multiplexed as one plugin. Qt is not aware of the switching.
>
> Yeap, this is a situation, but there is another one we should
> consider: dynamic switching qt-immodule, such as between uim-qtimm and
> scim-qtimm in the same application? I think qt-immodule infracture
> should support this, won't it?
I also think so. immodule-qt will be desirable to support a dynamic
switching between qtimms. But, Qt should be not aware of this switching.
(Only input method currently used needs to know. Only input method
currently used needs to know.)
> > > - prevention of choosing the module in appliation in use
> >
> > I can't understand what you mentioned. Please show me a scenario
> > as example.
>
> IMO, one example is: a qt-immodule plugin (say scim-qtimm) can only
> handle CJK (in fact can also handle some other ones) input methods,
> then it makes no sense to display this plugin in a context-menu under
> other locales (other then utf-8, of course)
> So I think this suggest us to have some properties support in
> qt-immodule, such as what languages it can handle etc.
My idea is making impossible selection of the input method which the
error took place in the application. Of course, other applications should
not be affected. (This is about error handling.)
> BTW: I do not think a Language() function in inputcontext is a good
> practice, maybe we should do it in a more generic way, such as a
> generic query API, so we can add/delete properties without breaking BC
> or adding new APIs.
I thought that it was good to use this method of QInputContext as follow.
QInputContextFactory::makeIMSelectPopupMenu()
{
qic->language();
}
Probably, this will not break BC.
--
Daisuke Kameda <kaminmat at cc.rim.or.jp>
More information about the immodule-qt
mailing list