Kas, So sorry for making my very personal confusing code public! The many lines per line is indeed me trying to optimize for screen space, grouping things together once I'm sure they're working. NOTE: Kids, don't do this yourselves. Only crusty old timers get to write code that looks unstructured and confusing :-) PICO actually refers not to the editor, but rather a whole series of small expressive controllers based on real-world objects I built back in the 90's. See: http://www.cs.princeton.edu/~prc/PICOSlide.jpg I do indeed use pico the editor, but one has nothing to do with the others. I have lately (Since NIME at CMU) taken to making a MAUI "Dashboard" for every controller I use, demo, (and hopefully every one I've ever made). The dashboard code checks for MIDI input, and if it's there it uses the data from the controller to update the controls on screen. This helps me debug the controller connections, individual sensors, battery, etc. If there is no MIDI seen, then the code switches over to just hanging out waiting for the user to move sliders and click buttons on the interface. This allows me to write and work on performance pieces on the airplane or other places where getting out the controller and plugging it in would be inconvenient (or get me arrested and sent to terrorist camp). PRC On Oct 1, 2012, at 9:00 AM, chuck-users-request@lists.cs.princeton.edu wrote:

Send chuck-users mailing list submissions to chuck-users@lists.cs.princeton.edu

To subscribe or unsubscribe via the World Wide Web, visit https://lists.cs.princeton.edu/mailman/listinfo/chuck-users or, via email, send a message with subject or body 'help' to chuck-users-request@lists.cs.princeton.edu

You can reach the person managing the list at chuck-users-owner@lists.cs.princeton.edu

When replying, please edit your Subject line so it is more specific than "Re: Contents of chuck-users digest..."

Today's Topics:

1. Re: Begin the beguine (Alberto Alassio) (Kassen) 2. Re: Begin the beguine (Alberto Alassio) (Alberto Alassio)

----------------------------------------------------------------------

Message: 1 Date: Mon, 1 Oct 2012 05:28:16 +0200 From: Kassen To: ChucK Users Mailing List Subject: Re: [chuck-users] Begin the beguine (Alberto Alassio) Message-ID: <20121001032815.GF1526@gmail.com> Content-Type: text/plain; charset=us-ascii

On Sun, Sep 30, 2012 at 07:01:24PM -0700, Perry Cook wrote:

...

Hey all,

Hey Perry,

...

I'll pipe in here with a set of course notes I put together for a workshop/tutorial on "Sonification in ChucK" It steps through chuck from Hello Sine through functions and built-in math.foo() and std.bar() functions through much more.

Very nice indeed!

...

It is, I believe, the most short yet complete list of things you can and should do with ChucK. Not everything is explained, of course (it was only a 2 hour tutorial).

I am curious about this; http://www.cs.princeton.edu/~prc/ChucKU/Code/SonificationExamples/PICOBoxDas...

I notice that you are quite often putting two or more lines of ChucK code on a single screen line. Sometimes those statements are clearly closely related pairs perhaps not worth a "for" loop, at other points I'm left wondering. Are you optimising for fitting as many things as possible on screen? That might make sense if "PICO" refers to the editor which -from memory- supports a lot more than most think, but not setting marks to jump to.

No critique, genuinely curious.

Yours, Kas.

------------------------------

Message: 2 Date: Mon, 1 Oct 2012 10:58:19 +0200 From: Alberto Alassio To: ChucK Users Mailing List Subject: Re: [chuck-users] Begin the beguine (Alberto Alassio) Message-ID: Content-Type: text/plain; charset="iso-8859-1"

now that I know what it means I can say : yes!

On Mon, Oct 1, 2012 at 4:21 AM, Renato Fabbri wrote:

...

Alberto AlassioAA fan? http://wiki.nosdigitais.teia.org.br/AA_%28English%29

2012/9/30 Perry Cook

...

Hey all,

I'll pipe in here with a set of course notes I put together for a workshop/tutorial on "Sonification in ChucK" It steps through chuck from Hello Sine through functions and built-in math.foo() and std.bar() functions through much more. It is, I believe, the most short yet complete list of things you can and should do with ChucK. Not everything is explained, of course (it was only a 2 hour tutorial).

It's all on a sub-directory of my main web page called "ChucK U!"

See: http://www.cs.princeton.edu/~prc/ChucKU/

The notes are at:

http://www.cs.princeton.edu/~prc/ChucKU/SonifyingInChucKICAD2012.pdf

but if you go to the main ChucKU page, you'll see code examples, links to other things, etc.

PRC

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- GNU/Linux User #479299 labmacambira.sf.net

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users