Issue 1514 in ibus: ibus-daemon should reload when engines are added or removed.

[ib...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 1514 by TiagoMa...@gmail.com: ibus-daemon should reload when
engines are added or removed.
http://code.google.com/p/ibus/issues/detail?id=1514

Currently ibus-daemon doesn't seem to notice that engines have been added
or removed. It would be nice if it did.

[ib...@googlecode.com]

Comment #1 on issue 1514 by daiki.u...@gmail.com: ibus-daemon should reload

when engines are added or removed.
http://code.google.com/p/ibus/issues/detail?id=1514

If you mean install or uninstall by "added or removed", ibus-daemon can
emit "RegistryChanged" D-Bus signal when any file under the component
directory is modified.

Old ibus gtk2 panel showed a notification:
https://github.com/ibus/ibus/blob/master/ui/gtk2/main.py#L61

Note that --monitor-timeout option is needed for this feature.

[ib...@googlecode.com]

Comment #2 on issue 1514 by TiagoMa...@gmail.com: ibus-daemon should reload

when engines are added or removed.
http://code.google.com/p/ibus/issues/detail?id=1514

Ugh, polling... and we'd have to tell the bus to restart. I don't think
that's acceptable, ibus should really handle all of this internally and
just emit a signal so that clients can reload when stuff changes.

[ib...@googlecode.com]

Comment #3 on issue 1514 by hade...@gmail.com: ibus-daemon should reload

when engines are added or removed.
http://code.google.com/p/ibus/issues/detail?id=1514

Why do we need to use monitor timeout? Can't ibus use inotify to get
directory change events? That's possible using GIO, or even using raw
inotify with glib, for example:
http://git.kernel.org/?p=bluetooth/bluez.git;a=blob;f=plugins/adaptername.c;h=cd0ffb2e2b59d6703f901a26adf44414571591bd;hb=HEAD#l274

[ib...@googlecode.com]

Updates:
Labels: Component-ibus

Comment #4 on issue 1514 by damage3...@gmail.com: ibus-daemon should reload

when engines are added or removed.
http://code.google.com/p/ibus/issues/detail?id=1514

Cool, you pointed out a long lasting issue!

[ib...@googlecode.com]

Comment #5 on issue 1514 by daiki.u...@gmail.com: ibus-daemon should reload

when engines are added or removed.
http://code.google.com/p/ibus/issues/detail?id=1514

As we discussed on IRC, it may be not so easy to reload engines list
implicitly, while using GFileMonitor would be straightforward.

So I would like to address this issue separately (1) avoid polling and (2)
reload engines list automatically.

Here is the first round of patch:
https://codereview.appspot.com/6589065

[ib...@googlecode.com]

Updates:
Status: Fixed

Comment #6 on issue 1514 by takao.fujiwara1: ibus-daemon should reload when

engines are added or removed.
http://code.google.com/p/ibus/issues/detail?id=1514

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[ib...@googlecode.com]

Updates:
Status: Accepted

Comment #7 on issue 1514 by daiki.u...@gmail.com: ibus-daemon should reload

when engines are added or removed.
http://code.google.com/p/ibus/issues/detail?id=1514

Obviously, not fixed yet.

[ib...@googlecode.com]

Comment #8 on issue 1514 by takao.fujiwara1: ibus-daemon should reload when

engines are added or removed.

https://code.google.com/p/ibus/issues/detail?id=1514

File a new bug for the left issue.

[ib...@googlecode.com]

Updates:
Status: WontFix

Comment #9 on issue 1514 by takao.fujiwara1: ibus-daemon should reload when

engines are added or removed.
https://code.google.com/p/ibus/issues/detail?id=1514

(No comment was entered for this change.)