>What I wasn't able to do was end arbitrary
shreds in the Mini's console monitor without using the mouse (and thus depend
on visual feedback), you can navigate the table of shreds using only the
keyboard and >all fields are labelled in plain text but on my Linux install
I couldn't get the keyboard control to go to the table itself and hitting
enter on the field that should remove the shred didn't do a thing.
Yes, if
there was a keyboard command to bring focus to the table of schreds and
keyboard commands for removing and whatever else you can do with each schred,
theis would help tremendously.
>How far would those two additions
get you? I think those would be nice to have for anyone and might especially
enable people on a screen reader to navigate the whole program and those
wouldn't require >anything near the effort of a whole re-write of the
Audicle.
Agreed, I think they would be very helpful additions.
From altern's message on this thread, it seems
that Java Swing will interface with OSC, and Sun has put a lot of work into
making this toolkit accessible. Thus, when you use a standard swing control in
your program, Java knows how to:
1. keyboard enable this by default
2. communicate the state of the control to the
access technology (screen reader)
I'll have to check this out more thuroughly.
Perhaps it would be more effective to write the UI in Java, but XUL just seems
to be a natural for writing UIs.
In any case, thanx for all the responses to my
message. I'll post more when I've tried a few things...
-- Rich
----- Original Message -----
Sent: Monday, November 19, 2007 6:01
PM
Subject: Re: [chuck-users] Controling
Chuck - building accessible GUI
Rich,
You only mention the Audicle
and not the MiniAudicle. The Mini is considerably more simple, I never used a
screen reader but as far as I can see the Mini uses very straightforward text
labels with the exception of a few icons that are also reachable by hotkeys.
What I wasn't able to do was end arbitrary shreds in the Mini's
console monitor without using the mouse (and thus depend on visual feedback),
you can navigate the table of shreds using only the keyboard and all fields
are labelled in plain text but on my Linux install I couldn't get the keyboard
control to go to the table itself and hitting enter on the field that should
remove the shred didn't do a thing.
How far would those two additions
get you? I think those would be nice to have for anyone and might especially
enable people on a screen reader to navigate the whole program and those
wouldn't require anything near the effort of a whole re-write of the Audicle.
Much like Stephen I find the whole question quite mysterious, I never
used a screen reader but my first guess would be that a a plain text editor
with a command-line should be a perfect match for one, perhaps I don't
understand completely what you are after?
To answer your other
question, you won't get a thing out of ChucK without writing some code but the
good news is that per line of code you can get a lot of sound. On the forum
we've been playing a game of getting the most interesting sounds out of one or
two 80 character lines with very interesting results, in a few paragraphs you
could write a small synth controlled by MIDI or a joypad and from there on
it's good riddance to the whole screen with regard to playing music. I can't
imagine the exact nature of your challenge but I would guess that ChucK might
well suit your needs.
Yours,
Kas.
_______________________________________________
chuck-users mailing
list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users