The hacked code would detect whether AppIndicator exists.
So we got race condition as a final result.
A better approach of supporting IBus and other IM framework is using a separate UI.
The UI can be very native to DE concerned and it communicates with the IM framework concerned through DBus.
Hi, all.
I've just done "apt-get source ibus" and skimmed the code a little bit.
I found that Ubuntu hacked origin IBus code a little bit to support Application indicators. developer. ubuntu. com/resources/ technologies/ application- indicators/
http://
Origin IBus uses "old school" GtkStatusIcon.
The hacked code would detect whether AppIndicator exists.
So we got race condition as a final result.
A better approach of supporting IBus and other IM framework is using a separate UI.
The UI can be very native to DE concerned and it communicates with the IM framework concerned through DBus.
I've found four existing examples: /github. com/tualatrix/ fcitx-gimpanel (DE: Unity, IMF: Fcitx) /github. com/fujiwarat/ ibus-gjs (DE: GNOME, IMF: IBus) userbase. kde.org/ Tutorials/ Kimpanel (DE: KDE, IMF: Multiple) /github. com/csslayer/ kimpanel- for-gnome- shell (DE: GNOME, IMF: Multiple)
https:/
https:/
http://
https:/