[Bug 879942] Re: Enabling on screen keyboard in GNOME Shell starts both caribou and onboard

[Jeremy Bicha]

Marmuta, I agree that GNOME Shell & Classic are very different desktops
and they are becoming more different with each GNOME release as GNOME
adopts new technologies that no one bothers to port to the old desktop.
Those names are part of the freedesktop desktop menu spec which can be
changed (MATE was added fairly recently, I don't see Cinnamon yet
though): http://standards.freedesktop.org/menu-spec/latest/apb.html

Yes, updating the spec would fix this bug but I don't think that will
happen in time for 12.10.

Since GNOME Shell hard-depends on caribou, it's not really practical to
use an alternate screen keyboard there. Maybe the GNOME developers would
consider allowing alternate screen keyboards since their built-in
keyboard is very lacking.

I guess it shouldn't be a hard ban though because it's possible to run
onboard without having the org.gnome.desktop.a11y.applications screen-
reader-enabled key set. Maybe onboard should not automatically start if
that key is set and it can detect that it's running in Shell, but
manually running onboard should still work.

-- 
You received this bug notification because you are a member of
Accessibility, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/879942

Title:
  Enabling on screen keyboard in GNOME Shell starts both caribou and
  onboard

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/879942/+subscriptions