https://bugzilla.redhat.com/show_bug.cgi?id=847500
--- Comment #3 from Allan Day <allanpday(a)gmail.com> ---
(In reply to comment #1)
(In reply to comment #0)
> An on-screen keyboard should be presented as part of the system, and should
> be fully integrated into the user experience. GNOME Shell already comes with
> an integrated on-screen keyboard: Eekboard shouldn't be necessary, provides
> overlapping functionality, and results in an extra application launcher.
First of all, I agree with not installing eekboard on default English system.
Currently it is installed as a dependency of ibus-m17n, which had required
iok before to input Indic characters. So I guess we could restrict the
installation only for Indic languages. Let me check comps.
The GNOME Shell on-screen keyboard should integrate with whatever input source
is being used [1]. That said, it seems strange that eekboard is specifically
tied to ibus-m17n. I'd be interested to know if there is a reason for this.
Asking around, no one seems to be able to give me an answer to that.
> If the GNOME Shell on-screen keyboard is missing any necessary
> functionality, we should file bugs against it and get it up to scratch.
Actually I filed some bugs and patches some months ago but no response so
far:
https://bugzilla.gnome.org/show_bug.cgi?id=673547
https://bugzilla.gnome.org/show_bug.cgi?id=673579
Is the component still actively maintained?
Unfortunately not. I hope that that will changes in the future.
[1]
https://bugzilla.gnome.org/show_bug.cgi?id=681735
--
You are receiving this mail because:
You are on the CC list for the bug.