Here is another excellent example of the use of video for prototyping, by Anab Jain and Louise Klinker, both graduates of the Royal College of Art’s Design Interactions MA program. The project was also featured in Bill Buxton’s book “Sketching User Experiences”.
Today’s lab gave me trouble, but not from the coding: This time, I found the actual physical setups confusing. However, after much troubleshooting, checking and double-checking connections, etc., everything worked just as it should.
For those of you playing at home, view the lab here.
“When two people start a conversation, they usually begin talking alike within a matter of seconds,” says James Pennebaker, professor of psychology at the University of Texas at Austin. “This also happens when people read a book or watch a movie. As soon as the credits roll, they find themselves talking like the author or the central characters.”
Because style matching is automatic, it serves as an unobtrusive window into people’s close relationships with others.
Style matching has the potential to quickly and easily reveal whether any given pair of people — ranging from business rivals to romantic partners — are psychologically on the same page and what this means for their future together.
Does style matching extend beyond language to fashion? To food? To travel preferences? It would explain a great deal.
It took me a while to get going on this lab, but I think I generally understand what’s going on now. I worked with Erin, which definitely helped (having someone to bounce things off, commiserate/celebrate with). I did have to check out code from the previous class’ work, but doing so really helped me understand exactly what I was doing.
Definitely the best part of the lab was constructing Snoopy… I think he’s so cute! In all seriousness though, I am much more comfortable with static and linear things (like drawing, or simple timeline type drawing) vs. the variable type things (like the bouncing ball).
One thing I failed at pretty epically was resizing Snoopy. I eventually got it to work by creating a float variable for size, and then working to apply that throughout the drawing. However, I initially tried using scale();, which works, sort of. I wanted to be able to use it to define the size change once across the entire draw function, which worked. But, it breaks the system down because it doesn’t reset, and it continues to affect whatever follows after it (even outside of that function, which I don’t understand).
One really helpful hint: when drawing in Processing, it’s better/easier to lay out your drawing first in Photoshop, with each shape in a different layer. Once your drawing is complete, reset the document’s origin to wherever you want the origin to be in Processing. Then, when coding your shapes, simply show the origination points of each shape in Photoshop to give how many pixels you have to add to your xPosition or yPosition. This definitely saved me some serious time when coding Snoopy (who has quite a number of shapes).