ICM continues with a steep learning curve. This week, we work on interaction.
Up until now, most of my preparation is invested on watching Shiffman’s video. Still, I have to watch some of the video twice to grasp ideas. I only wish he could edit out some of the rumble-mumble. Learning to write with proper syntax takes time. Something simple as putting blocks of code under setup or draw can make a huge difference. What I end of doing is not only take notes on whiteboard, but also create processing files to write down the example he demonstrated. The purpose of that is I can have something to go back to if I get stuck three weeks from now.
This week, I have trouble understanding boolean variable, so I made an appointment with Roopa. She clarified by describing the boolean as a switch, when the switch is on, certain execution will happen. When the switch is off, the opposite happens. However, it is only when you make a boolean=false, things get complicated and frizzled.
David and I work together to brainstorm. David suggested he likes something simple with dynamics, so we decided to go with Pong. Next, we spent almost three hours to discuss how objects would interact and writing codes to achieve that. Whee neither of us know how to make ellipses bounce off rectangle and not fall through, we made another appointment with Roopa for assistance.
I was enlightened by videos on modularity and reusebility. I only wish they can introduced elements such as global/local variables or boolean variable first in the first part of syllabus. Reason being, some of the lecture in the beginning are details on scale. Being a beginner on coding, it would help so much if someone can explain things from a bigger picture and work on details later.
(Processing file to be uploaded.)