Monday, 30 May 2011
Thursday, 26 May 2011
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.
Monday, 23 May 2011
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.
Sunday, 22 May 2011
Project 3 - update
instead of using models looking at using cubecraft, due to time constraints and cost factors and ease of use
Monday, 16 May 2011
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
--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
Wednesday, 11 May 2011
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
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
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 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
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
- 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.
- Information-hiding: By interacting only with an object's methods, the details of its internal implementation remain hidden from the outside world.
- 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.
- 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
Sunday, 1 May 2011
Project2 - Final(2)
http://openprocessing.org/visuals/?visualID=27876
Link to my openprocessing sketch.
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.
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.
Thursday, 14 April 2011
Project 2 - update7 (before presentation)
I have followed my initial plan of allowing the user to create the object that generates the noise, and by giving the user the ability to move the light when its night time, but also put an element of surprise by randomising the night/day transition.
Project 2 - update6
I have managed to incorporate sound into my sketch using "soundcipher", a sound library that I have found to be much simpler to use then minim. I have got basic sound interaction on moth hitting the flame but need to try and expand this into a more immersive experience.
I also made the light on/off transition automatic because I felt that making the user control this transformation was making it an unpleasant experience, when they also made the moths. this has allowed me to expand on my code by randomising the day to night transition during moth creation, and using the second() function to time the night to day transition.
I also made the light on/off transition automatic because I felt that making the user control this transformation was making it an unpleasant experience, when they also made the moths. this has allowed me to expand on my code by randomising the day to night transition during moth creation, and using the second() function to time the night to day transition.
Wednesday, 13 April 2011
Project 2 - update5
i have modified my code to limit the amount of moths that can be created, this way i can automate some other functions I want to implement such as the light turning of (day to night) being an automatic process on "moths created = x" and also the opposite, night to day, on "moths destroyed = x".
have also randomised the velocity of moths on creation, makes it a bit more natural.
have also randomised the velocity of moths on creation, makes it a bit more natural.
Monday, 11 April 2011
Project 2 - update4
I've managed to incorporate some sound into the transformations, but still need to play with it plenty to get it tweaked right.
Monday, 4 April 2011
Sunday, 3 April 2011
Project 2 - update2
i have the basic program going, with objects flying into a central object, took me awhile to figure out the trigonometry to achieve it but i got there eventually! my next task is to work out how to move the central object and have the little objects fly towards it once its set.
Thursday, 31 March 2011
Wednesday, 30 March 2011
Project 2 - initial presentation
the idea that i've settled on is having a central object, and other smaller objects surrounding it which can be created with mouse clicks, these objects make a noise. as these smaller objects float towards the central object the noise they produce gets higher. when the right mouse is clicked all the smaller objects float around randomly and there pitch goes back to normal. when they reach the central object the smaller objects die.
I came up with this idea through coding a processing program that closely resembles the bouncing balls video shown in the lecture. i liked the idea of allowing the user to create the objects that make the noise, thus giving them the power of whats produced.
I came up with this idea through coding a processing program that closely resembles the bouncing balls video shown in the lecture. i liked the idea of allowing the user to create the objects that make the noise, thus giving them the power of whats produced.
Tuesday, 29 March 2011
Project 2 - ideas (part ii)
another idea is using minim to create waves of music, and having mouse controls to place effects on top of the music
Project 2 - ideas
my first idea is to create a galaxy, closely entwined, and when sounds happen (eg mousepressed) the planets explode out. my idea came from this openprocessing project.
http://www.openprocessing.org/visuals/?visualID=8213
my second idea is to use particles to create a cloud, and the colors of the particles change around where the interaction occurs, also playing a sound
my third idea is to have a line that moves across the screen, left to right, and jumps up and down with noise or interaction.
my fourth idea comes from the video we watched at the end of lecture 5. where the mouse is pressed a ball is created and drops, when it hits the bottom a noise is made. i'l play around with different sizes and weights against gravity.
http://www.openprocessing.org/visuals/?visualID=8213
my second idea is to use particles to create a cloud, and the colors of the particles change around where the interaction occurs, also playing a sound
my third idea is to have a line that moves across the screen, left to right, and jumps up and down with noise or interaction.
my fourth idea comes from the video we watched at the end of lecture 5. where the mouse is pressed a ball is created and drops, when it hits the bottom a noise is made. i'l play around with different sizes and weights against gravity.
Monday, 28 March 2011
Transformation
Transformation - Join
http://www.openprocessing.org/visuals/?visualID=18414
I thought this processing code was pretty cool because of its simplicity. reminds me of a bank vault locking.
The codes very simple, just uses rectangles with different opacitys, and mouseX to calculate the movements to make the left and right sides meet.
http://www.openprocessing.org/visuals/?visualID=18414
I thought this processing code was pretty cool because of its simplicity. reminds me of a bank vault locking.
The codes very simple, just uses rectangles with different opacitys, and mouseX to calculate the movements to make the left and right sides meet.
Programming The Bigger Picture
Programming is required by designers to achieve things that need: variation, interaction, generation, repetition, calculation, and scalability.
Being able to understand theses principles will help me form my ideas into usable designs, could be used to create a platform to make the coding process easier.
My experience with code is that if you "think" that you can do something, eg. make a ball bounce off a table, then there is a way of doing it, it's a matter of breaking it into steps and tackling each step one by one, eg. ball starts at top, moves down at x speed, hits table, bounces up at y speed. What I need to figure out is what color the ball is, and what the tables made out of.
Being able to understand theses principles will help me form my ideas into usable designs, could be used to create a platform to make the coding process easier.
My experience with code is that if you "think" that you can do something, eg. make a ball bounce off a table, then there is a way of doing it, it's a matter of breaking it into steps and tackling each step one by one, eg. ball starts at top, moves down at x speed, hits table, bounces up at y speed. What I need to figure out is what color the ball is, and what the tables made out of.
Tuesday, 22 March 2011
Reflection - Project 1
Through developing the wallpapers I have learnt to not be so constrained in what I want to achieve through design with my coding. By experimenting and trying different approaches new possibilities open up.
I was motivated by the output that coding can produce, and creating images that weren't necessarily exactly what I was aiming for, to create often surprising results.
Something that I need to improve on for the next project is having a clearer idea from the start of what I want to achieve for the project, this way I will be able to push my code and design into a certain direction, and will create a good platform to develop off.
My goal for my next project is to create something more creative, I felt that my first project was to simplistic in design.
I was motivated by the output that coding can produce, and creating images that weren't necessarily exactly what I was aiming for, to create often surprising results.
Something that I need to improve on for the next project is having a clearer idea from the start of what I want to achieve for the project, this way I will be able to push my code and design into a certain direction, and will create a good platform to develop off.
My goal for my next project is to create something more creative, I felt that my first project was to simplistic in design.
Sunday, 20 March 2011
Details of wallpapers
The wallpapers i have created expand on each previous iteration, the first of which is a simple line pattern. developing of this I introduced some arcs on top of selected lines for the 2nd wallpaper, and also enlarged the lines to have it look more zoomed in. Triangles were also added across the background because i felt that it provided some order to the background texture. for the 3rd wallpaper i added ellipses to selected rows to add additional detail to the wall, and again enlarged the lines. the final wallpaper is again enlarged and provides a far more detailed view of the pattern.
The background was created by randomising the color of points between 2 shades of beige. I created it this way because I wanted to give it a rough look like real wallpaper, rather than flat colours.
I put opacity on most elements of the code such as the lines, triangles, and ellipses because I felt that this helped push the shapes into the background giving it a more wallpaper-y look.
The background was created by randomising the color of points between 2 shades of beige. I created it this way because I wanted to give it a rough look like real wallpaper, rather than flat colours.
I put opacity on most elements of the code such as the lines, triangles, and ellipses because I felt that this helped push the shapes into the background giving it a more wallpaper-y look.
Open Processing
Here's links to the Open Processing site wallpapers. There's an issue with how they're appearing, the code isn't running through smoothly on the processing website.
Wallpaper1
http://openprocessing.org/visuals/?visualID=24278
Wallpaper2
http://openprocessing.org/visuals/?visualID=24279
Wallpaper3
http://openprocessing.org/visuals/?visualID=24280
Wallpaper4
http://openprocessing.org/visuals/?visualID=24281
Wallpaper1
http://openprocessing.org/visuals/?visualID=24278
Wallpaper2
http://openprocessing.org/visuals/?visualID=24279
Wallpaper3
http://openprocessing.org/visuals/?visualID=24280
Wallpaper4
http://openprocessing.org/visuals/?visualID=24281
Theme 2
An issue that has arisen is the similarities between the four wall paper codes, as they build on the same structure, but i have countered this by adding more advanced elements to each code such as nested FOR loops.
Theme 2
Building off the theme of having a progression from straight lines to curves I've had an idea of using perspective to show the same image from differing distances, each one going into more detail and showing more intricacies in the pattern.
This idea has come from looking at real wallpapers.
This idea has come from looking at real wallpapers.
Saturday, 19 March 2011
Theme
From the initial presentation of my sketches I've come away with the theme of a progression from straight lines to full on curves.
An idea I had for displaying this progression is through a heart beat monitor because the link between the pictures is clearly defined when viewing.
I have to keep playing with code to develop this idea.
An idea I had for displaying this progression is through a heart beat monitor because the link between the pictures is clearly defined when viewing.
I have to keep playing with code to develop this idea.
Thursday, 10 March 2011
Tuesday, 8 March 2011
Thursday, 3 March 2011
First code design yo
http://openprocessing.org/visuals/?visualID=22453
First processing code.
I like purple.
First processing code.
I like purple.
Subscribe to:
Posts (Atom)