Monday, 9 May 2011

Project 3 - pre 5

program that allows the user to fill in variables to make an object act in different ways. shows the modularity of objects

Project 3 - pre 4

pixels, magnets, photos

Project 3 - pre 3

class is a blueprint for object
object is an instance of the class

- blueprint pic (car blueprint)
- object pic (proper car with color)
- run time movement (car doing stuff)

or

- blueprint of armyman
- object is individual armymen all lined up
- run time is armymen moving round

Thursday, 5 May 2011

Project 3 - pre 2

Focus on
  1. Modularity: The source code for an object can be written and maintained independently of the source code for other objects. Once created, an object can be easily passed around inside the system.
  2. Information-hiding: By interacting only with an object's methods, the details of its internal implementation remain hidden from the outside world.
  3. Code re-use: If an object already exists (perhaps written by another software developer), you can use that object in your program. This allows specialists to implement/test/debug complex, task-specific objects, which you can then trust to run in your own code.
  4. Pluggability and debugging ease: If a particular object turns out to be problematic, you can simply remove it from your application and plug in a different object as its replacement. This is analogous to fixing mechanical problems in the real world. If a bolt breaks, you replace it, not the entire machine.

Tuesday, 3 May 2011

Project 3

I'm thinking of classes and objects,

cookie cutter, cookie

Sunday, 1 May 2011

Project2 - Final(2)

http://openprocessing.org/visuals/?visualID=27876

Link to my openprocessing sketch.

Project2 - Final

I have built my 2nd project around the moths to a flame idea with two main transformation processes, the life/death of the moths, and the transition of day/night. My visuals clearly show the night/day transition through the background color change from blue (day) to black (night), and the color change of the light from being off during the day period, and on during the night period.
Sound has been incorporated into the design on the creation and death of each moth. On creation I have used a piano sound that chooses random notes picked from the Egyptian Scale. I choose this scale and the piano because I wanted something soft and pleasent sounding to represent the moths creation, but I also wanted it to be darker as a whole, which the Egyptian scale achieves. On the death of each moth I have used a drum sound because it contrasts with the soft piano sound, providing a contrast between the life and death of the moth.
The mouse movement interactions that I have incorporated has 3 elements to it. The most obvious of these is the creation of each moth on mouse click. I have done this because it gives the user the ability to control the life element of my project. The second, but more subtle, is that the moths follow the mouse point during the day period. I incorporated this because bugs always have a habit of lingering around where you are. The third interaction is the ability to move the light during the night period. I incorporated this because I wanted the user to also have some control in the death of each moth, as they have full control in creating the moth. When you click and drag on the light it moves it around the screen. This provides a way for the user to have a sense of control in both the life and death of the moth, and they can choose whether to keep the light away from the moths, keeping them alive during night, or destroying the moths.