Comment 30 for bug 983254
Revision history for this message
| Yu Ning (yuningdodo) wrote Re: Unity use ibus explicitly, make it impossible to use other input method | #30 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
@csslayer
Hi, before I actually work on something I did had compared your branch and paulliu', and my first attempt is to merge paulliu's XIM patch to your branch, to provide InputMethodXim. However I failed to do that. The problem was I didn't found some proper way to handle events. But I think I could try this again, and hope I can managed it this time.
Any way, I think it is not a perfect idea to write a InputMethodXxx for each IM, neither to add support inside each IM for nux's input method interface. Both ways have a problem, that even if we add support for N input methods, the user may want to use a (N+1)th one.
So in my personal opinion, to support the currently most widely used IM protocols, XIM, GtkIMContext, QT..., should be a lazy but acceptable way, almost every input method support at least one of them. However it may be impossible, or at least hard, to support gtk/qt, because we never know if a nux window is a GdkWindow, QWindow, or just a raw nux window.
However I support your solution on split nux's input method to an interface with some implements. It did looks hacky & strange on current ibus support or xim support.