GNOME Bugzilla – Bug 646980
Core/UI separation
Last modified: 2011-06-08 20:10:42 UTC
Sorry if i should have put this elsewhere. In a project i work on (not open - one day hopefully) we make extensive use of the gnome stack however not gtk, we have a purely clutter/mx environment, i've found the need to implement my own touchscreen/remote powered on-screen keyboard as i don't want to rely on gtk and in general i can't sufficiently theme existing solutions to look like they integrate into my environment. This is not overly difficult however is extremely limited and integrates only with the application it is included and in its current form will never do things like import new keyboard layouts, or word autocomplete like i saw mentioned as an enhancement idea. I'm interested to know if caribou can be designed in such a way that GTK is not at its core. Essentially caribou could load keyboard layouts, handle virtkey, gsettings, atspi etc as a library and the GTK representation, preferences window etc as an application. I realize that there is not much interest in catering for people working on closed applications, however in talking with clutter people they have no standard way of handling this situation and a Clutter Caribou Keyboard would be very useful.
This is not my module, but given the interest (and growing developments) in the area of accessibility for other desktop environments, this might be worth pursuing. We have begun work in Orca to separate out the gui from our core code so that we can work in GNOME 2, GNOME 3, KDE, and XFCE. If all a11y tools were able to do this sort of thing, GNOME a11y could become *nix a11y. And personally I think that would be extremely cool.
I am going to say that this is fixed in HEAD. Caribou right now is heavily modularized and used for the non-GTK GNOME Shell keyboard.