[chuck-users] Controling Chuck - building accessible GUI
altern2 at gmail.com
Mon Nov 19 16:44:56 EST 2007
Rich Caloggero(e)k dio:
> There was a thread on this list back in January about control of chuck
> via OSC, a Python package. I have a few questions:
> First, I'm blind and use a screen reader. I want to build something that
> allows me to control chuck sreds via a GUI. I don't like Python much
> for programming, and am not sure if OSC would even work with my screen
> reader (anyone have any quick demos I could try just to see if the
> screen reader will deal with the UI toolkit at all)?
I am not sure I understand what you mean. So I will just do some remark.
OSC is just a network protocol that has been implemented in many
different languages. I always suggest Python because I think the Python
OSC implementation is quite easy to use but you could use OSC from many
other languages such as Java, C, Perl, Ruby and so on ...
Check this link below for a list of languages that have OSC
implementations, not all are languages, some are applications of frameworks
For example Reaktor does have OSC implemented. But this is graphical
like PD and MAX as well.
So OSC does not have a UI at all. Many different UI implemented on
different languages can be used to create interfaces that later send
OSC. For example Python and Tk, C and WxWidgets, Java and Swing, and so
on. There are many combinations. Each has advantages and disadvantages.
I guess in you case you should check which widgets toolkits work with
your screen reader and then choose a language that can be used with that
toolkit. Also check that the languages fulfils your needs. This is a
list of toolkits at Wikipedia
The ones that work for C and C++ are usually ported to scripting
languages such as Python, Perl, Ruby and so on. For example Tk and FLTK
are very simple to use.
hope this helps somehow
> What I was thinking of doing is building something in Mozilla's XUL
> language. This does have the ability to send network packets, and also
> can execute shell commands. So, was thinking about writing code in
> chuck and then pass arguments to each .ck file to change parameters. Of
> course, this might not work so smoothly if we wanted to change things on
> the fly. FOr this I guess I'd need to implement something like OSC's
> message passing scheme in XUL.
> Any advice, or suggestions? Anyone interested in rewriting audical so
> it works with a screen reader? There are so many great software
> synthesizers on the market now that work as both stand alone and/or
> plugins to popular hosts like Cakewalk's Sonar, but none that I've ever
> tried will allow the screen reader enough control to do real sound
> design. With effort, one can usually figure out how to change presets,
> but in a large number of cases even this is not possible. I was hoping
> that chuck could be used to build a fully accessible sound designers
> toolbox that could allow one to do things quickly and easily without
> having to write too much code. I've obviously never used it because it
> is very graphically oriented, but think of something like PD "Pure
> Data". You aparently can build all sorts of neat stuff by just plugging
> stuff together, without having to write a line of code.
> Thanx for any thoughts/suggestions...
> -- Rich
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
More information about the chuck-users