SOK: The plan as I see it

Henrik Nilsen Omma henrik at ubuntu.com
Sun May 14 21:01:18 UTC 2006


Chris Jones wrote:
> The Keyboard itself we be rendered using Cairo.
>
> Instead of trying a one size fits all solution using only xlib and
> cairo, we target Gnome.  We keep the keyboard rendering and AT-SPI
> related code as separate as possible to make porting to other toolkits
> easier.
>
> No GOK code will be used since it would not give us much benefit over
> the  AT-SPI bindings and would complicate things significantly.
>
> Keyboard layout will probably be much more fine-grained than GOK and
> using GOK's xml files will limit us feature-wise.  Extending the GOK
> xml wouldn't be much use since it would not be backwards compatable to
> GOK itself.  Our application should use it's own xml file format and
> be able to convert from GOK's format to it's own.
>
Sounds like a good plan. I would add that we write it in pure python 
unless a very good reason comes along for using some C.

So to summarise the summary:

 * Python code from scratch
 * Cairo rendering of keys
 * Use the GTK toolkit, but as little as possible
 * Native XML keyboard format
 * Use AT-SPI as appropriate
 * Implement our own sticky keys solution

Hey folks, that's Milestone 0 done!

- Henrik




More information about the Ubuntu-accessibility mailing list