interface so that a)
the GUI and back-end are kept separate and b) so that it can run either
as a separate program or as an integrated part of a common config panel?
If so, we should be able to build a Speech Dispatcher interface using
the same principles, followed by KTTS and other ATs. The big
Hynek Hanke wrote:
I'd like to propose to move this thread to
[EMAIL PROTECTED]
so that it is not spread across several mailing list,
people know where to post replies and we have an archive.
The mailing list at Freedesktop currently has subscribes
from a wide range of accessibility
that porting and integration can be
accommodated later.
So, is this realistic? Can we construct the Orca interface so that a)
the GUI and back-end are kept separate and b) so that it can run either
as a separate program or as an integrated part of a common config panel?
If so, we should be able
Small tangent...
Brian Cameron wrote:
Henrik:
I do not think that this completely solve the how do I set
my accessibility preferences when I can't do anything until the
preferences are set up.
Perhaps a set of hotkeys are necessary to launch the different
accessibility tools so that a user
David:
Use of gestures would be nice. Are gdm style gestures on the radar
for desktop session usage?
I don't think so.
Brian
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
Gary Cramblitt píše v Ne 23. 04. 2006 v 14:52 -0400:
Once KTTS migrates to using Speech Dispatcher as its backend, I envision a
single GUI for configuring it and Speech Dispatcher, since they will be
closely related. I'm thinking therefore, that instead of two icons KTTS
and Speech
Gary Cramblitt wrote:
An interesting idea. Just a couple of quick thoughts.
Once KTTS migrates to using Speech Dispatcher as its backend, I envision a
single GUI for configuring it and Speech Dispatcher, since they will be
closely related. I'm thinking therefore, that instead of two icons
