Processing: Creative Coding and Computational Art

createRect(50, 50, 100, 100, 20, 5, 100);
}
// parameterized function
void createRect(int xpos, int ypos, int wdth,
int ht, int strokeCol,
int strokeWt, int fillCol) {
stroke(strokeCol);
strokeWeight(strokeWt);
fill(fillCol);
rect (xpos, ypos, wdth, ht);
}
Both sketches should output the same centered rectangle, as shown in Figure 3-8.
Figure 3-8. Rectangle generated initially using magic
numbers and then with a function
Do you see how the second approach will allow you to create any rectangle, while the first
only creates one? The more modular and general you can make your code, the greater the
chance you can reuse it or easily expand it. However, this type of approach takes more
planning and analysis, and sometimes you just want to get coding. Because this book is
about creative coding, I think it is perfectly acceptable to sometimes hack out poorly
structured, “ugly” code, especially if it allows you to express yourself and find new solutions
more effectively. I suspect if you’re like me, you’ll eventually discover things that you
want to build out into larger projects, and that’s where the rules and best practices stuff
becomes important. So basically you have permission from me to write nasty code when
necessary (to remain creatively engaged), but don’t rat me out to your teacher or boss
when they give you a hard time about it.
CODE GRAMMAR 101
103
3