IBus new Control+Space window

Recently I updated ibus to 1.4.99.20120203-3 in Fedora 17 or later.
The ibus is not available in upstream yet but we would need the new ibus for Fedora 17. It enhances:

  • Performance of Control+Space.
  • New Control+Space GUI window.
  • IBus indicator can work without ibus-daemon on gnome-shell to handle XKB only.

Previously ibus-daemon handles the trigger key, Control+Space, and some of the performance problems were happened when input method engines are switched. Now the ibus status icon on panel handles Control+Space and I hope the performance issue was fixed.

Previously the trigger key switches a previous ibus engine and next engine. Now the trigger key behaves to switch multiple engines likes Alt+Tab. If you use Control+Shift+Space, the reverse switching is called. The following is the new window with ibus GTK:
IBus Switcher Window with ibus-ui-gtk3
The following is the new window with ibus-gnome3 on gnome-shell:
IBus Switcher Window with ibus-gnome3 on gnome-shell
IBus menu with ibus-gnome3 on gnome-shell
IBus lookup window with ibus-gnome3 on gnome-shell

Requirements:

# yum install ibus ibus-gnome3 gnome-shell gjs
# rpm -q ibus gnome-shell gjs
ibus-1.4.99.20120203-3.fc17.x86_64
gnome-shell-3.3.5-1.fc17.x86_64
gjs-1.31.10-1.fc17.x86_64

Currently we use the devel branch with ibus and ibus-gjs git and when the upstream is updated, I will move the devel branch to master.

About these ads

About fujiwara

I'm an open-sourced desktop i18n developer.
This entry was posted in IBus and tagged , , , . Bookmark the permalink.

8 Responses to IBus new Control+Space window

  1. bochecha says:

    Wow, that alt-tab-like GNOME-Shell-themed window to chose input methods looks great!

    Do you think the integration in upstream GNOME (GNOME Shell + GNOME Control Center) will be finished for GNOME 3.4 / Fedora 17?

    The input method handling is really the last thing I’m not confident with switching my girlfriend to GNOME 3 (from Windows 7), I’d love to do that for Fedora 17. :)

  2. Ding-Yi Chen says:

    Personally,I prefer to use alt-shift to trigger this feature.

    • fujiwara says:

      The previous Alt+Shift has a problem. E.g. if the preload_engines are us, pinyin, anthy, the default switch was us and pinyin and if you pressed Alt+Shift, the next switching was pinyin and anthy but not us and anthy. The new Control+Space resolve the problem so that the pair engine is not changed since you keep pressing Control key.

  3. allarem says:

    Bravo work!
    But I encounter while configure. I’m a Ubuntu newbie :)

    sudo ./configure -prefix=/usr -datadir=/usr/share
    .....
    Build options:
    Version 3.2.1.20120227
    Install prefix /usr
    Enable standalone yes
    HAVE IBus XKB false
    IBUS XKB
    GNOME_SHELL_VERSION 3.2
    GJS_VERSION 1.30

    Even I force install, the lookglass will show “no module ‘ibus’….”
    what did I miss?

    • fujiwara says:

      I think Ubuntu ibus doesn’t provide /usr/lib*/girepository-1.0/IBus-1.0.typelib .
      You need to install ibus from the source code with ./configure –prefix=/usr –enable-introspection .

  4. For the OSD selection window, the one or two character summary is not satisfactory enough.
    “酷” for ibus-chewing is good since libchewing project call itself “新酷音”.
    “中“ for ibus-pinyin is too vague, it should be “拼”.

    For the drop down menu, I don’t think language name need to be displayed.
    What user would concern is which engine is currently active, rather than which language the current active engine offers.
    Mac OS X’s drop down menu display engine name and a small icon only.

  5. fujiwara says:

    > “酷” for ibus-chewing is good since libchewing project call itself “新酷音”.

    The menu does not express each input method but the language prefix. It does not distinguish the engines in the same language.
    So keymap engines are shown as ASCII prefix (e.g. ‘en’, ‘fr’, ‘jp’) and input method engines are shown as multi-byte char.
    Actually myself does not mind which character is used in input methods but it would be good to use the same char in the same language.
    It would be good to discuss which one char is the best in your language engine.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s