19 Jan
2005
19 Jan
'05
noon
Janina Sajka <janina(a)rednote.net> writes:
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. Actually, by using--if you have stuck with--stock GTK2
widgets, you may
have already achieved this. Wouldn't that be something?
Yes, it would.
I know we have at least a couple of custom widgets, one for meters and
one for the hand-drawn graphical EQ.
Jan Depner (who wrote most of our GUI interface) made the same point
to me off-list. We would certainly like to see this happen.
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.
Thanks for the offer.
With testing and knowledgeable consulting assistance, it looks like
this could be done more easily than I had realized.
--
joq