Hi Colton. Well, wouldn't classify myself as a guru, but I have programmed in chuck a fair amount, and am also blind, so I totally get your frustration! What kind of things are you wanting to do with it? The most frustrating part for me is no gui support - not in terms of integrated development environments, but for the running chuck program itself. Apparently, audical can be used as a GUI for the running chuck program as well as development. I tried two approaches to solve this, neither vary optimal: using chuck events to listen to keyboard directly and then build a simple set of single character commands. For instance: up/down arrows to adjust a value and tab to tab among parameters. All output was simply written to the standard output which the screen reader would read, most of the time... the second used a node.js server to communicate with chuck via OSC (open sound control), and with a web browser. The browser ran the GUI which allowed tabbing among parameters and changing values, and the server would turn messages from the program running in the browser to OSC commands which chuck could act upon. This was better, but in my opinion has too many moving parts as it were: too complicated... -- Rich From: Colton Hill Sent: Sunday, September 04, 2016 1:01 PM To: chuck-users@lists.cs.princeton.edu Subject: [chuck-users] anybody still use this thing? Yo, it's Colton. I am a 15 year old boy in the US, and I am blind. ChucK has been the only audio language I can pick up and use, thanks to it's command line support. The mini audical is completely unusable, just like other ides for things such as super collider. I do have some questions about chuck, and I was wondering if anybody still used this thing that would be willing to answer. I need a guru! _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users