Today was different in that sense that my teammate decided it was best if we split up and did the the project separately. Which I’m a bit surprised over because mostly, if not all of the time, I have been developing the material/code. I’m just a bit confused as to what the motivation behind the move is. These things certainly happen all the time in a professional setting too, the important part is that the knowledge gained during the time we worked together is shared.
Continuing on from where I last left off was that some kind of object has to interact with the user and so I came up with the idea of using a balloon as the object. Which technically wouldn’t be hard to program, just a colored circle with a straight cord.
In order to create meaningful and coupled interaction, the movement that the user makes has make sense and offer a dynamic interaction. While I was trying out different movements I found that my pace was as if the balloon had some imaginary weight to it. The speed and force I used in figure 1 was more of trying to push air upwards to keep the balloon floating and moving. This made sense in a way, kind of like keeping a feather floating in the air. The point of keeping the balloon floating is to keep it in your possession, if the user stops to “generate” air the balloon would fall down to the ground.
In some way the interactive component is to keep generating air to keep the balloon floating, the force of the movement isn’t as important as the nuance of speed. Doing faster circular motions should generate more air and keep the balloon floating for a longer period of time or maybe it blows away from the frame? There is a couple of different scenarios I want to try out, as usual the only thing I fear is that programing will be a hinderance to try out those things.
Micro blogg 