It's a lovely piece of software but, coming out of the box, it does not really fit my typical workflow. The problem? It's an IDE. I can't stand IDEs. Not only do I have to learn a new language but I have to learn a whole new toolkit for working in it. I much much prefer being able to compose a script in my favorite text editor and then summon that script from the command line.
Fortunately Processing supports this workflow. I found this post at dsfcode.com that does a great job of describing how to set it up. And once I had done so it becomes so easy to get into my usual edit/run/re-edit cycle.
The only thing to watch out for is that the order of parameters in the
processing-java command matters. So this command succeeds:
$ processing-java --sketch=`pwd`/waveclock/ \ > --output=`pwd`/../outputs/waveclock/ \ > --force --run Finished
but this does not:
$ processing-java --sketch=`pwd`/waveclock/ \ > --output=`pwd`/../outputs/waveclock/ \ > --run --force The output folder already exists. Use --force to remove it.
By the way, the sketch that I am running is a slight modification of case study 4.2 in Pearson's "Generative Art" and its output is shown above. My code is here.