AMY E MARTIN // Blog

We're working with Processing in both of my interactive studios right now so my brain wants to combine the projects. For my early class we're still working on clocks. For my later class, we're still working on valentines. I seem to have combined the camera code from the valentines with the clock dot code I was working on for the clocks and we have camera clock! The computer vision aspect of this clock is more or less superfluous. The squares rotate and lighten with each second of the clock but it isn't really that spectacular of a *thing*. I like the dots clock part (the clock below reads 01:03:43 for example) but I didn't create that either. I just copied it from a clock I saw over the holidays.

Primarily, I've been trying to condense my code. Processing has hour(), minute(), second() functions which makes it super easy to read from the computer's system clock but there is such a huge repetition of functions that there must clearly be a way for an actual programmer (as opposed to me, the hack) to write this code in a few lines instead of 500. Go object oriented programming for designers who are like, "huh?!"

Also, say hello to my straight forward analog clock. After spending WAY too much time trying to figure out the math for getting Processing to read milliseconds from the system clock instead of from when the program started, I just imported a java library that does all that for me and so I got a smooth second hand. Of course, I kept seeing a petri-dish in my old clock so I took out the numbers, turned the face hands (lines) into points and drew a bunch of random dots on the background. Petri-dish clock enabled!

And yeah, at some point, whenever I have the portfolio part of this site done, I will upload actual working applets instead of these screenshots. The programs are way more fun when they're bouncing and moving around.