Reference updates for PShape, noise(), blend(), and createShape()

REAS · REAS · commit c729d5e7da0f · 2015-10-02T21:35:01.000-07:00
diff --git a/content/api_en/PShape.xml b/content/api_en/PShape.xml
@@ -32,7 +32,7 @@ void draw() {
 PShape square;  // The PShape object
 
 void setup() {  
-  size(100, 100, P2D);
+  size(100, 100);
   // Creating the PShape as a square. The corner 
   // is 0,0 so that the center is at 40,40 
   square = createShape(RECT, 0, 0, 80, 80);
diff --git a/content/api_en/PShape_beginContour.xml b/content/api_en/PShape_beginContour.xml
@@ -14,7 +14,7 @@
 PShape s;
 
 void setup() {
-  size(100, 100, P2D);
+  size(100, 100);
 
   // Make a shape
   s = createShape();
diff --git a/content/api_en/PShape_beginShape.xml b/content/api_en/PShape_beginShape.xml
@@ -14,7 +14,7 @@
 PShape s;  // The PShape object
 
 void setup() {  
-  size(100, 100, P2D);
+  size(100, 100);
   s = createShape();
   s.beginShape();
   s.fill(0, 0, 255);
diff --git a/content/api_en/PShape_endContour.xml b/content/api_en/PShape_endContour.xml
@@ -14,7 +14,7 @@
 PShape s;
 
 void setup() {
-  size(100, 100, P2D);
+  size(100, 100);
 
   // Make a shape
   s = createShape();
diff --git a/content/api_en/PShape_endShape.xml b/content/api_en/PShape_endShape.xml
@@ -14,7 +14,7 @@
 PShape s;  // The PShape object
 
 void setup() {  
-  size(100, 100, P2D);
+  size(100, 100);
   s = createShape();
   s.beginShape();
   s.fill(0, 0, 255);
diff --git a/content/api_en/PShape_getVertex.xml b/content/api_en/PShape_getVertex.xml
@@ -14,7 +14,7 @@
 PShape s;
 
 void setup() {
-  size(100, 100, P2D);
+  size(100, 100);
   s = createShape();
   s.beginShape();
   s.vertex(0, 0);
@@ -38,7 +38,7 @@ void draw() {
 </example>
 
 <description><![CDATA[
-The <b>getVertex()</b> method returns a PVector with the coordinates of the vertex point located at the position defined by the <b>index</b> parameter. This method works when shapes are created as shown in the example above, but won't work properly when a shape is defined explicitly (e.g. createShape(RECT, 20, 20, 80, 80).
+The <b>getVertex()</b> method returns a PVector with the coordinates of the vertex point located at the position defined by the <b>index</b> parameter. This method works when shapes are created as shown in the example above, but won't work properly when a shape is defined explicitly (e.g. <b>createShape(RECT, 20, 20, 80, 80)</b>.
 ]]></description>
 
 </root>
diff --git a/content/api_en/PShape_getVertexCount.xml b/content/api_en/PShape_getVertexCount.xml
@@ -14,7 +14,7 @@
 PShape s;
 
 void setup() {
-  size(100, 100, P2D);
+  size(100, 100);
   s = createShape();
   s.beginShape();
   s.vertex(0, 0);
diff --git a/content/api_en/PShape_setVertex.xml b/content/api_en/PShape_setVertex.xml
@@ -14,7 +14,7 @@
 PShape s;
 
 void setup() {
-  size(100, 100, P2D);
+  size(100, 100);
   s = createShape();
   s.beginShape();
   s.vertex(0, 0);
@@ -38,7 +38,7 @@ void draw() {
 </example>
 
 <description><![CDATA[
-The <b>setVertex()</b> method defines the coordinates of the vertex point located at the position defined by the <b>index</b> parameter. This method works when shapes are created as shown in the example above, but won't work properly when a shape is defined explicitly (e.g. createShape(RECT, 20, 20, 80, 80).
+The <b>setVertex()</b> method defines the coordinates of the vertex point located at the position defined by the <b>index</b> parameter. This method works when shapes are created as shown in the example above, but won't work properly when a shape is defined explicitly (e.g. <b>createShape(RECT, 20, 20, 80, 80)</b>.
 ]]></description>
 
 </root>
diff --git a/content/api_en/blend.xml b/content/api_en/blend.xml
@@ -84,7 +84,7 @@ Called "Color Dodge" in Illustrator and Photoshop.<br />
 BURN - Darker areas are applied, increasing contrast, ignores lights.
 Called "Color Burn" in Illustrator and Photoshop.<br />
 <br />
-All modes use the alpha information (highest byte) of source image pixels as the blending factor. If the source and destination regions are different sizes, the image will be automatically resized to match the destination size. If the <b>srcImg</b> parameter is not used, the display window is used as the source image.<br />
+All modes use the alpha information (highest byte) of source image pixels as the blending factor. If the source and destination regions are different sizes, the image will be automatically resized to match the destination size. If the <b>src</b> parameter is not used, the display window is used as the source image.<br />
 <br />
 As of release 0149, this function ignores <b>imageMode()</b>.
 ]]></description>
diff --git a/content/api_en/createShape.xml b/content/api_en/createShape.xml
@@ -14,7 +14,7 @@
 PShape square;  // The PShape object
 
 void setup() {
-  size(100, 100, P2D);
+  size(100, 100);
   // Creating the PShape as a square. The
   // numeric arguments are similar to rect().
   square = createShape(RECT, 0, 0, 50, 50);
@@ -34,7 +34,7 @@ void draw() {
 PShape s;  // The PShape object
 
 void setup() {
-  size(100, 100, P2D);
+  size(100, 100);
   // Creating a custom PShape as a square, by
   // specifying a series of vertices.
   s = createShape();
@@ -85,7 +85,7 @@ void draw() {
 PShape alien, head, body;
 
 void setup() {
-  size(100, 100, P2D);
+  size(100, 100);
 
   // Create the shape group
   alien = createShape(GROUP);
diff --git a/content/api_en/include/float.xml b/content/api_en/include/float.xml
@@ -21,15 +21,18 @@ float c = a + b;   // Declare variable 'c' and assign it the sum of 'a' and 'b'
 <example>
 <image></image>
 <code><![CDATA[
-float f = 0;
+float f1 = 0.0;
 for (int i = 0 ; i < 100000; i++) {  
-  f = f + 0.0001;  // Bad idea! See below.
+  f1 = f1 + 0.0001;  // Bad idea! See below.
 }
+println(f1);
 
+float f2 = 0.0;
 for (int i = 0; i < 100000; i++) {
-  // The variable 'f' will work better here, less affected by rounding
-  float f = i / 1000.0;  // Count by thousandths
+  // The variable 'f2' will work better here, less affected by rounding
+  f2 = i / 1000.0;  // Count by thousandths
 }
+println(f2);
 ]]></code>
 </example>
 
diff --git a/content/api_en/noise.xml b/content/api_en/noise.xml
@@ -25,13 +25,12 @@ void draw() {
 <example>
 <image></image>
 <code><![CDATA[
-float noiseScale=0.02;
+float noiseScale = 0.02;
 
 void draw() {
   background(0);
   for (int x=0; x < width; x++) {
-    float noiseVal = noise((mouseX+x)*noiseScale, 
-                            mouseY*noiseScale);
+    float noiseVal = noise((mouseX+x)*noiseScale, mouseY*noiseScale);
     stroke(noiseVal*255);
     line(x, mouseY+noiseVal*80, x, height);
   }
@@ -40,13 +39,15 @@ void draw() {
 </example>
 
 <description><![CDATA[
-Returns the Perlin noise value at specified coordinates. Perlin noise is a random sequence generator producing a more natural, harmonic succession of numbers than that of the standard <b>random()</b> function. It was invented by Ken Perlin in the 1980s and has been used in graphical applications to generate procedural textures, shapes, terrains, and other seemingly organic forms.<br />
+Returns the Perlin noise value at specified coordinates. Perlin noise is a random sequence generator producing a more natural, harmonic succession of numbers than that of the standard <b>random()</b> function. It was developed by Ken Perlin in the 1980s and has been used in graphical applications to generate procedural textures, shapes, terrains, and other seemingly organic forms.<br />
 <br />
 In contrast to the <b>random()</b> function, Perlin noise is defined in an infinite n-dimensional space, in which each pair of coordinates corresponds to a fixed semi-random value (fixed only for the lifespan of the program). The resulting value will always be between 0.0 and 1.0. Processing can compute 1D, 2D and 3D noise, depending on the number of coordinates given. The noise value can be animated by moving through the noise space, as demonstrated in the first example above. The 2nd and 3rd dimensions can also be interpreted as time.<br />
 <br />
 The actual noise structure is similar to that of an audio signal, in respect to the function's use of frequencies. Similar to the concept of harmonics in physics, Perlin noise is computed over several octaves which are added together for the final result.<br />
 <br />
-Another way to adjust the character of the resulting sequence is the scale of the input coordinates. As the function works within an infinite space, the value of the coordinates doesn't matter as such; only the <em>distance</em> between successive coordinates is important (such as when using <b>noise()</b> within a loop). As a general rule, the smaller the difference between coordinates, the smoother the resulting noise sequence. Steps of 0.005-0.03 work best for most applications, but this will differ depending on use.
+Another way to adjust the character of the resulting sequence is the scale of the input coordinates. As the function works within an infinite space, the value of the coordinates doesn't matter as such; only the <em>distance</em> between successive coordinates is important (such as when using <b>noise()</b> within a loop). As a general rule, the smaller the difference between coordinates, the smoother the resulting noise sequence. Steps of 0.005-0.03 work best for most applications, but this will differ depending on use.<br />
+<br />
+There have been debates over the accuracy of the implementation of noise in Processing. For clarification, it's an implementation of "classic Perlin noise" from 1983, and not the newer "simplex noise" method from 2001.  
 ]]></description>
 
 </root>
