I would like to start a discussion on using Processing as a Natural Language Experience
A friend of mine once said that coding should be like talking to one another. However, verbally talking is a primitive form of communication. You have the pronunciation , connotation and context issues to get past. Coding allows you to get past these three layers and provide an environment that saves both time and increase the usability.
Processing's core strength in my opinion lies in its pixel array. Processing is so powerful it needs a simple yet strong but flexible backbone by which to operate. I believe that is it pixel array.
The pixel array can be used for a number of purposes. It is predominately used for manipulating pixel data aka (r,g,b,a)
red, green , blue , alpha values.
However, one of the popular techniques of mine is storing data in the pixel array, albeit text, audio even motion and time. Any data set stored within the confines of 0 to 255 and a four chamber matrix [0..255,0..255,0..255,0..255] can be stored in an .png file saved to the hard drive, email to someone, instantaneously loaded using the Loadimage() command and once that application is based on the same premise of execution as insertion was used, you have a quasi-universal format by which to operate.
Now the only problem I have found with Processing; is that due to it's power and flexibility it is quite easy to achieve better results from mistakes that what you originally intended to create. A variable not reset at the right time, a positive value used instead of a negative... stuff like that. I find that you have to be quite focused otherwise
Processing will take over (for the lack of a better analogy)
Quite often, I have found myself of coming up with an idea on the fly while coding something totally unrelated to the sketch.
2D images are my forte. 3D is ok but we all we are doing really is manipulating a 3D image on a 2D surface our lcd monitor or screen. It's quite ironic that the best 3D image is based off a black and white image using varying r,g,b,a values to adjust the brightness; wherein the brightness - represents the z-axis. Albeit crude, but it works.
Programming in Processing is even simpler than Visual Basic.
A friend of mine once said that coding should be like talking to one another. However, verbally talking is a primitive form of communication. You have the pronunciation , connotation and context issues to get past. Coding allows you to get past these three layers and provide an environment that saves both time and increase the usability.
Processing's core strength in my opinion lies in its pixel array. Processing is so powerful it needs a simple yet strong but flexible backbone by which to operate. I believe that is it pixel array.
The pixel array can be used for a number of purposes. It is predominately used for manipulating pixel data aka (r,g,b,a)
red, green , blue , alpha values.
However, one of the popular techniques of mine is storing data in the pixel array, albeit text, audio even motion and time. Any data set stored within the confines of 0 to 255 and a four chamber matrix [0..255,0..255,0..255,0..255] can be stored in an .png file saved to the hard drive, email to someone, instantaneously loaded using the Loadimage() command and once that application is based on the same premise of execution as insertion was used, you have a quasi-universal format by which to operate.
Now the only problem I have found with Processing; is that due to it's power and flexibility it is quite easy to achieve better results from mistakes that what you originally intended to create. A variable not reset at the right time, a positive value used instead of a negative... stuff like that. I find that you have to be quite focused otherwise
Processing will take over (for the lack of a better analogy)
Quite often, I have found myself of coming up with an idea on the fly while coding something totally unrelated to the sketch.
2D images are my forte. 3D is ok but we all we are doing really is manipulating a 3D image on a 2D surface our lcd monitor or screen. It's quite ironic that the best 3D image is based off a black and white image using varying r,g,b,a values to adjust the brightness; wherein the brightness - represents the z-axis. Albeit crude, but it works.
Programming in Processing is even simpler than Visual Basic.