Caribou Week 1

Dear blog,

I have been spending the last while working exclusively on Caribou, trying to get it out of the miserable shape it is in and make sure that it not only remains relevant, but really shines. I have been doing this for two weeks. But the first week was mostly spent on chasing down this bug in GDK. So I really only got down to business this last week.

Here is a photo:

What I have done:

  • Created an introspectable C library, initially to do the keyboard emulation and XKB stuff, but I have grand plans for it. What already landed in master is just simple key synth methods to replace Caribou’s reliance on python-virtkey which was never approved as GNOME external dependency.
  • Created an experimental git branch with a revamp of how we do layout in Caribou. Users will no longer choose between layouts, this is inferred from the current keyboard group the X server is set to. If the user will have any choice it will be between geometries, either a more natural geometry similar to what you have on tablets, or a fuller keyboard emulation.
  • Made “sub keys”, all the latest screen keyboards seem to do this, so now Latin accents and Semitic vowels could be easily entered.

Ok blog, I have to go. I’ll need to write a brief roadmap of where I think we should take this, and how Caribou could play a role in GNOME Shell, etc.

Here is a screencast of what Caribou looks like today.

Caribou Week 1

3 thoughts on “Caribou Week 1

  1. Nice! I must try using the Shell on my IdeaPad with the keyboard folded away and this.

    I’ve been trying to think for a while how to make compose sequences discoverable. I wonder if the answer might be to add hints to that on-screen keyboard: so when a user who has, and uses, their hardware keyboard cracks out the on-screen keyboard to enter é, add a little note saying “Hey! Did you know you can type AltGr-e or Compose-‘-e to type é?”

    (Or maybe it lives in gucharmap.)

Comments are closed.