Yes, swing I know is quite accessible. Not sure about AWT.
I will look at the I will test the code you sent this weekend sometime. I
need to install java here.
thanx Michael.
-- R
-----Original Message-----
From: Michael Heuer
Sent: Friday, February 07, 2014 1:38 PM
To: ChucK Users Mailing List
Subject: Re: [chuck-users] Listener
Hello Rich,
That is great feedback. Most Processing libraries I use for
communication with ChucK (p5osc, rwmidi, Midibus) also work outside of
Processing
http://www.sojamo.de/libraries/oscP5/
https://github.com/wesen/rwmidi
http://smallbutdigital.com/themidibus.php
so the UI could be written in java with either AWT or Swing controls,
both of which have strong accessibility support (although I have not
needed to depend on it).
Personally I don't like using a mouse or touchscreen; I was drawn to
ChucK in the first place because I could do everything from an editor
and the command line. And then building your own hardware with real
sliders and buttons and knobs is not very difficult or expensive any
more. For example, this costs less than $20
A Very Simple DIY USB MIDI Controller
http://little-scale.blogspot.com/2012/10/a-very-simple-diy-usb-midi-controller.html
michael
On Fri, Feb 7, 2014 at 11:50 AM, Rich Caloggero <[email protected]> wrote:
OK, as a blind user I feel I have to weigh in on this one. None of these
solutions are at all accessible. Of course, it probably doesn’t matter if
its a research project or for personal use (unless of course the author is
also a screen reader users), but I feel it needs to be said. Ironically
enough, Music, and sound processing / generating software in general, is
one of the least accessible categories of software out there.
I’m sure that Python has a widgit/gui library that’s accessible (the NVDA
screen reader is written in Python and uses these widgits extensively for
its own gui), but can’t remember what its called now. You could also write
the UI in html, but then you’d need node.js with web sockets to translate
the tcp messages to UDP for OSC.
The miniaudical is not accessible, and neither is processing from what I’ve
seen.
Just my two cents.
-- Rich
From: Joel Matthys
Sent: Friday, February 07, 2014 9:25 AM
To: [email protected]
Subject: Re: [chuck-users] Listener
You could create the sliders in Tcl/Tk and direct the output to ChucK on
the
command line; there's a good example of that with the piece "Granite09" in
the PlorK repository: http://plork.cs.princeton.edu/Repository/PLOrk.zip
Another option is to build a user interface in Processing
(http://processing.org) and send the slider values as OSC messages to
ChucK.
The OSC documentation for ChucK is pretty good; there's a section in the
manual and a few samples in the examples folder.
Joel
On 02/07/2014 12:47 AM, Philipp Blume wrote:
I am looking to implement a listener into my (very simple) ChucK program.
I
want to operate a bank of virtual sliders that send their position to
ChucK.
In what program/application can I build such a slider, and where in the
ChucK API can I read up on listeners? I don't yet know my way around the
documentation, though I do have the Kapur, Cook, Salazar, & Wang text
which
is wonderful.
Thanks in advance!
Philipp Blume
_______________________________________________
chuck-users mailing list
[email protected]
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
________________________________
_______________________________________________
chuck-users mailing list
[email protected]
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________
chuck-users mailing list
[email protected]
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________
chuck-users mailing list
[email protected]
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________
chuck-users mailing list
[email protected]
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
