Friday, 7 November 2008

Processing Processed

We had Java in first year, but the only thing I remember about it was dragging myself out of a semi-drunk coma, into a lecture theatre I didn't know, with people from outside my course, to be taught a subject I didn't only fail to understand, but failed to see the relevance of.

Fast forward 4 years, and I'm now studying for a PhD looking at the intersection of art and computers. And what comes up, my old friend Java.

In particular, I'm referring to Processing.

I'll only post a few examples:

Videos by a coder/artist called Robert Hodgin.


...but the interest for me in Processing is that it is wholeheartedly and unashamedly a coding language, complete with classes, constructors, libraries, the works, but it is aimed squarely at artists and information designers.

This interests me: how do you build a coding intensive architecture for artists? How do you cross the notational/visual divide?

Another reason to try and understand processing a little more is that I am studying peoples craft practises whilst not producing anything on my own. It's easy to fall into the trap of simply believing what perceived experts say on a subject without trying it yourself.

So in an effort to understand the meaning making processes in using digital technologies in relation to craft, I am planning to try to pick up some Processing, and all the Java related fun that that will entail.

I propose to try and create a small Processing program to take into schools to show potential applicants to the IMD course what can be done is such fields as ubiquitous computing and reactive environments, using either video or sound and a projector to show them how something like Processing can manipulate an image on screen, or perhaps on a projector. Hopefully it will be visually impressive enough, whilst also being accessible enough to keep some wannabe rebellious teens entertained from both an art and computing perspective.

Next steps then. I think, even though this is a self set brief, I'll want to set down goals before simply diving into processing. Who's it for, what will it do, what hardware requirements are there, can we make it so the little 'darlings' wont break it etc. etc.

Should be fun.

No comments: