Project 3 - Presentation

Project 3 - Write Up

I have chosen Objects as my coding concept, focusing on how an Object is built from its Class. I have chosen this concept because it is a key element of object oriented programming and by providing people with a clear understanding of how Objects are treated by a program will hopefully give them a better understanding of this style of coding. An Object is an entity created by a predefined coded Class, allowing a program to build objects when required. The coded Class provides a blue print which the program uses to build an Objects initial State. Think of a Class as a Cookie Cutter, it provides the shape for the Cookie, and the Object is the Cookie once cut. By using a Class to create Objects it provides the program the ability to easily create multiple Objects with same or similar attributes. My exhibition piece demonstrates the process of building Objects from its Class by showing multiple paper block models as Objects in their constructed state, and the single blueprint of these Objects as the paper stencil used to cut out and fold to make the models, between which lies some deconstructed pieces of the models, allowing a person to take the role of the program to construct their own Object.

Project 3 - update

changed from model to one of thessse due to time and cost constraints. and these will be easy for people to make.

Project 3 - update

instead of using models looking at using cubecraft, due to time constraints and cost factors and ease of use

Project 3 - 17/05

--my coding concept is objects, focusing on how its built from it's class.

--the class is like a blueprint, so i had the idea of showing the building process of an object through a flow chart, from its blueprint to the finished object.

--after thinking a bit more on this idea i thought it was a bit too straight forward in showing the process.

--after brainstorming more i remembered model plane kits, how its like a blueprint, can take it apart and build the plane.



















--my idea is to create a model kit, to represent building an object from it's class

time/cost -- allocate time to design the kit, cost of materials- cardboard, printing

Project 3 - Preliminary

The programming concept that I'm going to use is Objects, I have chosen this because It's an integral part of Object Oriented Programming.
Seeing as the idea of an Object is quite literal I'm going to focus on how an Object is built from its Class and Sub-Classes creating the Objects State, and how an Objects Behavior is affected with Functions.
With this in mind I've put the development of Objects into steps and have thought of design ideas around this. The first step being defining the Class, the second step affecting the Class Attributes and Behavior, and the third step the output of the Object.

1st Idea - Cookie Cutter
Class - Cookie cutter
Attributes - Icing
Object - Cookies
*has no behavior

2nd Idea - Object Program
Class - Ball
Attributes - Velocity, direction, colour, size
Object - Moving ball
*time consuming

3rd Idea - Blueprint -> Flowchart Diagram -> Image

Class - Blueprint image (vehicle)
Sub-Class - Blueprint image (different types of vehicles)
Attributes - Flowchart (Color-coded for State Attributes and Behavior Attributes)
Object - Image of Selected vehicle
*a path showing the selection process from Class to Object
*got to come up with attributes

Would like to incorporate the flowchart into a program but time constraints
time management plan - get it done by the 27th
cost/equipment - wall to stick paper on, paper printed on

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

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.

Project 3

I'm thinking of classes and objects,

cookie cutter, cookie

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.