GNOME Bugzilla – Bug 82714
input method integration into the desktop.
Last modified: 2006-07-21 15:33:02 UTC
Package: gtk+ Severity: enhancement Version: 2.0.2 Synopsis: gtk-global signal of imcontext which detect im status Bugzilla-Product: gtk+ Bugzilla-Component: gtk Description: a local gnome hacker, ganadist - you know?, suggest that 'what about im monitor applet?' (like IME tray icon of Windows taskbar) 'cos his doing port of ami over gtk2. I tried a quick view on gtkimcontext reference but no affordable signal was found. I think a layer of im context routine can detect which im is now in active, and give the signal to other bonobo, for example, the im status monitor. it's possible at this moment of gtk? or need to implement new signal? ------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-23 03:25 ------- Reassigning to the default owner of the component, gtk-bugs@gtk.org.
How to integrate input module and keyboard selection nicely into the keyboard is definitely an open and interesting question; I don't think a single signal would really be all that is needed. (There were some threads about this on gtk-i18n-list)
Moving input method related bugs to input-methods component
*** Bug 90216 has been marked as a duplicate of this bug. ***
See comments in bug 90216
what about GdkAtom or similar ones? Ami the Korean input method has a patch to support imhangul_status_applet which is an applet for imhangul of imhangul.kldp.net. and GConf uses these Atoms to persist connection among preferences AFAIK. I suppose it'll be possible to set GtkIMContext global Atom to indicate status of IM modules.
I think we should close this bug; the general opinion is that the right approach for input method integration is to use a framework like iiimf or (more recently) scim, with a fixed input method module. To facilitate this, GTK+ 2.10 will have settings to hide the input method selection submenu from the context menus of entries and text views.
I don't like scim (just tried once). I have never tried iiimf but the server/client architecture seems overkill to me. So I'd propose another approach. GtkSettings could add another setting, namely "gtk-input-method-name". Ihe setting has no effect if "gtk-show-input-method-menu" is true. Otherwise GtkIMContext would listen to "gtk-input-method-name", ignore GTK_IM_MODULE and the rest (unless the input method associated with "gtk-input-method-name" is unavailable for some reasons). Another applications such as im applets could change input method easily just as theme change. Another way is just throw away "gtk-show-input-method-menu" and use "gtk-input-method-name" for both. If it's empty, it's similar to "gtk-show-input-method-menu" = true.