Processing: Creative Coding and Computational Art

PROCESSING: CREATIVE CODING AND COMPUTATIONAL ART
304
Of course, within the BurritoRecipe class, there could be additional methods and properties
relating, for example, to side dishes, calories, costs, and so on. In OOP, your class
design decisions are not unlike decisions you would make in the real world if you really
were to make, serve, sell, or eat a burrito.
Before you actually create your BurritoRecipe class, have a look at the basic framework
of a simple generic class:
class ClassName {
}
// properties
int property1;
float property2;
// constructors
ClassName(){
}
ClassName(int prop1, float prop2){
property1 = prop1;
property2 = prop2;
}
// methods
void setProperty1(int prop1){
property1 = prop1;
}
int getProperty1(){
return property1;
}
void setProperty2(float prop2){
property2 = prop2;
}
float getProperty2(){
return property2;
}
A class begins with the keyword class, followed by a legal identifier (the name) of the
class. The naming of classes follows the same naming rules described in Chapter 3. The
convention is to begin class names with a capital letter. When using a compound name (a
name made up of multiple words), such as ClassName, you also capitalize the initial letter
of any nested words. Following the class identifier is an open curly brace. The class is
closed with a final terminating curly brace, at the very bottom of the class. Between the
open and closed curly braces are the class’s properties, constructors, and methods.
The properties are variables declared within the class with a data type, an identifier, and an
optional initial value. (If you don’t assign an initial value, the properties are assigned