User:Fako Berkers/project1: Difference between revisions

From XPUB & Lens-Based wiki
Line 3: Line 3:


===Performance space as a computer===
===Performance space as a computer===
The note by Alexander Galloway on code as a language that is executable reminded me of John Cage and performances of him I heard about. He wrote instructions for his performers.
The note by Alexander Galloway on code as a language that is executable reminded me of John Cage and performances of him I heard about. He wrote instructions for his performers for example:


<tt>"In a situation provided with maximum amplification, perform a disciplined action"</tt>
<tt>"In a situation provided with maximum amplification, perform a disciplined action"</tt>
Line 15: Line 15:
END<br/>
END<br/>
</code>
</code>
If you approach these instructions from a code point of view you can borrow concepts from programming languages (for instance procedures) to shape the instructions. This will make the instructions work differently. In the case of borrowing the concept op procedures the instructions become more dynamic:
<code>
PROCEDURE openWindow()
BEGIN
performance.action = "open a window";
END
PROCEDURE closeWindow()
BEGIN
performance.action = "close a window";
END
BEGIN
openWindow();
closeWindow();
openWindow();
openWindow();
closeWindow();
END


Most people will know the work of John Cage and that of Allan Kaprow. LeWitt seems to be another artist concerned with code that executes art. I will have to broaden my knowledge about them and especially my knowledge about the people who came after them. The idea of performers being the medium where upon language is executed appeals me. I wonder how far this
Most people will know the work of John Cage and that of Allan Kaprow. LeWitt seems to be another artist concerned with code that executes art. I will have to broaden my knowledge about them and especially my knowledge about the people who came after them. The idea of performers being the medium where upon language is executed appeals me. I wonder how far this

Revision as of 16:36, 6 October 2010

Week 1 and 2

I have a few ideas that I might want to work on. Some are in really early stages and I will not share them yet. But two are a little bit more mature and I'll describe them briefly below.

Performance space as a computer

The note by Alexander Galloway on code as a language that is executable reminded me of John Cage and performances of him I heard about. He wrote instructions for his performers for example:

"In a situation provided with maximum amplification, perform a disciplined action"

You could translate these instructions into code like language like:

BEGIN
sound.level = sound.maxlevel;
performance.action = "a disciplined action";
END

If you approach these instructions from a code point of view you can borrow concepts from programming languages (for instance procedures) to shape the instructions. This will make the instructions work differently. In the case of borrowing the concept op procedures the instructions become more dynamic:

PROCEDURE openWindow() BEGIN performance.action = "open a window"; END

PROCEDURE closeWindow() BEGIN performance.action = "close a window"; END

BEGIN openWindow(); closeWindow(); openWindow(); openWindow(); closeWindow(); END


Most people will know the work of John Cage and that of Allan Kaprow. LeWitt seems to be another artist concerned with code that executes art. I will have to broaden my knowledge about them and especially my knowledge about the people who came after them. The idea of performers being the medium where upon language is executed appeals me. I wonder how far this