19 Jan
2005
19 Jan
'05
10:18 a.m.
Jack O'Quin writes:
Julien Claassen <julien(a)c-lab.de> writes:
So, all may not be lost in terms of an "eyes-free" interface.
Julien: Have you tried with Gnopernicus? Or with Orca?
I would try this myself, but I'm about to leave for a conference. I'll
see if I can get one of the handful of folks who've gotten comfortable
with Gnopernicus to take a look. It would be cool if Jammin turns out to
be accessible, without anyone knowing it. That is possible because of
the use of GTK2. If the widgets used are standard GTK2 it either already
is, or could easily be made so by providing object properties data.
It would work with ecasound in the same way, very
perfectly! BUT: I
am blind! So I can't use jamin, if jamin doesn't have the ncurses
interface the Jamin people where thinking about. Does it have that?
Sorry for misunderstanding, Julien.
No, JAMin has a purely visual GTK-2 graphical interface.
After release 1.0, we have talked about decoupling the GUI from the
DSP engine, perhaps expanding on our existing OSC support for scene
changes. This would probably provide a better way to provide more
accessible interfaces. I think it's a good idea. But, that won't
happen any time soon.
Actually, by using--if you have stuck with--stock GTK2 widgets, you may
have already achieved this. Wouldn't that be something?
Certainly, the accessibility requirements pretty much require this kind
of decoupling. Output and input requirements both should be supported by
virtue of the abstracted support provided via gtk2.
Of mainstream musician interest would be alternative controls mapped via
Gok, the Gnome Onscreen Keyboard. It would be worthwhile to check this
out--and I'll do what I can, but it will take a few days.
--
joq
--
Janina Sajka Phone: +1.202.494.7040
Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
Chair, Accessibility Workgroup Free Standards Group (FSG)
janina(a)freestandards.org http://a11y.org
If Linux can't solve your computing problem, you need a different problem.