Dasher and accessibility

[Matthew Garrett <mjg59-gap srcf ucam org>]

I've cleaned up my accessibility code in Dasher quite considerably now, 
so I'd be interested in getting some more testing. There are two main 
things:

1) Configure Dasher with --with-a11y --with-gtk2. After startup, select
"Control mode" in the options menu. Application menus can then be
controlled within Dasher from the control node at the bottom of the
screen, and if you have a recent enough at-spi characters will be output
into the focussed window.

2) Configure Dasher with --with-speech --with-gtk2. Dasher should now
speak completed words.

To get the source for this, check it out of CVS as described at 
http://www.inference.phy.cam.ac.uk/dasher/Develop.html .

Two major issues:

a) The tree building code in the GTK2 version is highly suboptimal, and 
takes really quite a long time to build the menu tree. I'll fix this 
once I'm awake enough to think it through (the Win32 code is pretty 
optimal here, or at least as optimal as is possible given their horrible 
accessibiltiy code)

b) The menu tree won't be rebuilt if applications appear or disappear. 
Fixing this isn't worth it until (a) is done, but at that point I assume 
there's some way of getting a callback if a new accessible application 
appears?

I'll be presenting this stuff at the UKUUG event in Edinburgh at the end 
of the month if anyone's planning on being there.
-- 
Matthew Garrett | mjg59 srcf ucam org