From 4aaf77eb30d69f42def5a75f5b6d6312b21f1586 Mon Sep 17 00:00:00 2001 From: gohai Date: Sat, 28 Jan 2017 20:32:12 -0800 Subject: [PATCH 1/2] Rename "OS X" to "macOS" Suggested by https://github.com/processing/processing/issues/4860 --- content/api_en/LIB_pdf/index.html | 2 +- content/api_en/displayDensity.xml | 2 +- content/api_en/environment/index.html | 8 ++++---- content/api_en/launch.xml | 2 +- content/api_en/mouseWheel.xml | 2 +- content/api_en/pixelHeight.xml | 2 +- content/api_en/pixelWidth.xml | 2 +- content/static/tutorials/data/index.html | 2 +- content/static/tutorials/eclipse/index.html | 2 +- content/static/tutorials/electronics/index.html | 2 +- content/static/tutorials/gettingstarted/index.html | 2 +- content/static/tutorials/overview/index.html | 2 +- download/_downloads.php | 12 ++++++------ generate/lib/XPath.class.php | 2 +- templates/template.cover.html | 2 +- 15 files changed, 23 insertions(+), 23 deletions(-) diff --git a/content/api_en/LIB_pdf/index.html b/content/api_en/LIB_pdf/index.html index 71fdf7f61..9633810b2 100755 --- a/content/api_en/LIB_pdf/index.html +++ b/content/api_en/LIB_pdf/index.html @@ -281,7 +281,7 @@ may improve the situation if the font is installed on the machine. - diff --git a/content/api_en/displayDensity.xml b/content/api_en/displayDensity.xml index 1eabe02e9..5f2e71814 100644 --- a/content/api_en/displayDensity.xml +++ b/content/api_en/displayDensity.xml @@ -26,7 +26,7 @@ void draw() { diff --git a/content/api_en/environment/index.html b/content/api_en/environment/index.html index 4d2e038d2..6fb7d771a 100644 --- a/content/api_en/environment/index.html +++ b/content/api_en/environment/index.html @@ -135,10 +135,10 @@
File
Prints the code inside the text editor.
  • Preferences
    Change some of the ways Processing works. (This item is located in the Processing menu - on Mac OS X.)
    • + on macOS.)
  • Quit
    Exits the Processing Environment and closes all Processing windows. (This item is - located in the Processing menu on Mac OS X.)
    • + located in the Processing menu on macOS.)
    Edit
    @@ -278,7 +278,7 @@

    The Processing Development Environment (PDE) is highly configurable. The most common preferences can be modified in the Preferences window, located in the File menu on - Windows and Linux and in the Processing menu on Mac Os X. The full list of preferences + Windows and Linux and in the Processing menu on macOS. The full list of preferences are stored in the "preferences.txt" file. This file can be opened and edited directly only when Processing is not running. You can find the location of this file on your computer by reading the bottom-left corner of the Preferences window. @@ -503,7 +503,7 @@

    Java Mode

    This mode makes it possible to write short programs to draw to the screen, but also enables complex Java programs as well. It can be used simply by beginners, but it scales to professional Java software development. Sketches written in this mode can - be exported as Java Applications to run on Linux, Mac OS X, and Windows operating systems. + be exported as Java Applications to run on Linux, macOS, and Windows operating systems.

    diff --git a/content/api_en/launch.xml b/content/api_en/launch.xml index 87b86e389..36ca39280 100755 --- a/content/api_en/launch.xml +++ b/content/api_en/launch.xml @@ -32,7 +32,7 @@ Attempts to open an application or file using your platform's launcher. The f
    This function (roughly) emulates what happens when you double-click an application or document in the macOS Finder, the Windows Explorer, or your favorite Linux file manager. If you're trying to run command line functions directly, use the exec() function instead (see below).

    -This function behaves differently on each platform. On Windows, the parameters are sent to the Windows shell via "cmd /c". On Mac OS X, the "open" command is used (type "man open" in Terminal.app for documentation). On Linux, it first tries gnome-open, then kde-open, but if neither are available, it sends the command to the shell and prays that something useful happens.
    +This function behaves differently on each platform. On Windows, the parameters are sent to the Windows shell via "cmd /c". On macOS, the "open" command is used (type "man open" in Terminal.app for documentation). On Linux, it first tries gnome-open, then kde-open, but if neither are available, it sends the command to the shell and prays that something useful happens.

    For users familiar with Java, this is not the same as Runtime.exec(), because the launcher command is prepended. Instead, the exec(String[]) function is a shortcut for Runtime.getRuntime.exec(String[]). The exec() function is documented in the JavaDoc in the PApplet class. ]]> diff --git a/content/api_en/mouseWheel.xml b/content/api_en/mouseWheel.xml index 02c01cd7a..7fb0f1367 100755 --- a/content/api_en/mouseWheel.xml +++ b/content/api_en/mouseWheel.xml @@ -26,7 +26,7 @@ void mouseWheel(MouseEvent event) { mouseWheel()     function returns positive values when the mouse wheel is rotated down (toward the user), and negative values for the other direction (up or away from the user). On OS X with "natural" scrolling enabled, the values are opposite. +The mouseWheel() function returns positive values when the mouse wheel is rotated down (toward the user), and negative values for the other direction (up or away from the user). On macOS with "natural" scrolling enabled, the values are opposite.

    Mouse and keyboard events only work when a program has draw(). Without draw(), the code is only run once and then stops listening for events. ]]> diff --git a/content/api_en/pixelHeight.xml b/content/api_en/pixelHeight.xml index 8be6e94d4..03c6fc3be 100755 --- a/content/api_en/pixelHeight.xml +++ b/content/api_en/pixelHeight.xml @@ -16,7 +16,7 @@ println(pixelWidth, pixelHeight); pixelDensity(2) is used to make use of a high resolution display (called a Retina display on OS X or high-dpi on Windows and Linux), the width and height of the sketch do not change, but the number of pixels is doubled. As a result, all operations that use pixels (like loadPixels(), get(), set(), etc.) happen in this doubled space. As a convenience, the variables pixelWidth and pixelHeight hold the actual width and height of the sketch in pixels. This is useful for any sketch that uses the pixels[] array, for instance, because the number of elements in the array will be pixelWidth*pixelHeight, not width*height. +When pixelDensity(2) is used to make use of a high resolution display (called a Retina display on macOS or high-dpi on Windows and Linux), the width and height of the sketch do not change, but the number of pixels is doubled. As a result, all operations that use pixels (like loadPixels(), get(), set(), etc.) happen in this doubled space. As a convenience, the variables pixelWidth and pixelHeight hold the actual width and height of the sketch in pixels. This is useful for any sketch that uses the pixels[] array, for instance, because the number of elements in the array will be pixelWidth*pixelHeight, not width*height. ]]> \ No newline at end of file diff --git a/content/api_en/pixelWidth.xml b/content/api_en/pixelWidth.xml index 45ab35d9e..de15f418b 100755 --- a/content/api_en/pixelWidth.xml +++ b/content/api_en/pixelWidth.xml @@ -16,7 +16,7 @@ println(pixelWidth, pixelHeight); pixelDensity(2) is used to make use of a high resolution display (called a Retina display on OS X or high-dpi on Windows and Linux), the width and height of the sketch do not change, but the number of pixels is doubled. As a result, all operations that use pixels (like loadPixels(), get(), set(), etc.) happen in this doubled space. As a convenience, the variables pixelWidth and pixelHeight hold the actual width and height of the sketch in pixels. This is useful for any sketch that uses the pixels[] array, for instance, because the number of elements in the array will be pixelWidth*pixelHeight, not width*height. +When pixelDensity(2) is used to make use of a high resolution display (called a Retina display on macOS or high-dpi on Windows and Linux), the width and height of the sketch do not change, but the number of pixels is doubled. As a result, all operations that use pixels (like loadPixels(), get(), set(), etc.) happen in this doubled space. As a convenience, the variables pixelWidth and pixelHeight hold the actual width and height of the sketch in pixels. This is useful for any sketch that uses the pixels[] array, for instance, because the number of elements in the array will be pixelWidth*pixelHeight, not width*height. ]]> \ No newline at end of file diff --git a/content/static/tutorials/data/index.html b/content/static/tutorials/data/index.html index d45a525a6..c5314dadd 100644 --- a/content/static/tutorials/data/index.html +++ b/content/static/tutorials/data/index.html @@ -183,7 +183,7 @@

    Working with Text Files

    - In order to create a text file, you can use any simple text editor. Windows Notepad or Mac OS X TextEdit will do; just make sure you format the file as “plain text.” It is also advisable to name the text files with the “.txt” extension, to avoid any confusion. And just as with image files, these text files should be placed in the sketch’s “data” directory in order for them to be recognized by the Processing sketch.

    + In order to create a text file, you can use any simple text editor. Windows Notepad or macOS TextEdit will do; just make sure you format the file as “plain text.” It is also advisable to name the text files with the “.txt” extension, to avoid any confusion. And just as with image files, these text files should be placed in the sketch’s “data” directory in order for them to be recognized by the Processing sketch.

    Once the text file is in place, Processing’s loadStrings() function is used to read the content of the file into a String array. The individual lines of text in the file each become an individual element in the array. diff --git a/content/static/tutorials/eclipse/index.html b/content/static/tutorials/eclipse/index.html index b5084926c..41c4e9fd9 100644 --- a/content/static/tutorials/eclipse/index.html +++ b/content/static/tutorials/eclipse/index.html @@ -35,7 +35,7 @@

    The idea of Libraries

    Import the Processing Core

    In order for Eclipse to see the code that makes up Processing, we need to import it into our project.

    File > Import > General > File System

    -

    Click next. On Windows, click "Browse..." and select the Processing jar files inside PATH_TO_PROCESSING/core/library/. On OS X, do not use the "Browse..." button. Instead, use the "From directory:" field to manually enter the path to Processing's jar files, which is typically /Applications/Processing 3.app/Contents/Java/core/library/. At minimum, select the "core.jar" file inside the "library" folder.

    +

    Click next. On Windows, click "Browse..." and select the Processing jar files inside PATH_TO_PROCESSING/core/library/. On macOS, do not use the "Browse..." button. Instead, use the "From directory:" field to manually enter the path to Processing's jar files, which is typically /Applications/Processing 3.app/Contents/Java/core/library/. At minimum, select the "core.jar" file inside the "library" folder.

    Importing the Processing Core

    A .jar file is a compiled collection of Java code. The core.jar is the core of the Processing libraries, it has all the code that does the stuff that we are used to doing in Processing, like drawing shapes. Once we have it, we can make use of all the normal Processing commands that are found on the reference page.

    Click Finish. If you look at the Package Explorer, you'll notice that there is a new file in our project, called 'core.jar'.

    diff --git a/content/static/tutorials/electronics/index.html b/content/static/tutorials/electronics/index.html index 9777b0f8f..5d08d7afd 100644 --- a/content/static/tutorials/electronics/index.html +++ b/content/static/tutorials/electronics/index.html @@ -273,7 +273,7 @@

    Sensors and communication

    - Because a device can have several serial ports, a user must specify which serial port to use for data transmission. On most Windows computers, serial port names are COMx, where x can be 1, 2, 3, etc. On UNIX-based systems (Mac OS X and Linux), serial devices are accessed through files in the /dev/ directory. After the serial port is selected, the user must specify the settings for the port. Communication speed will vary with devices, but typical values are 9600, 19,200, and 115,200 bits per second. Once the ports are open for communication on both devices, it is possible to send and receive data. + Because a device can have several serial ports, a user must specify which serial port to use for data transmission. On most Windows computers, serial port names are COMx, where x can be 1, 2, 3, etc. On UNIX-based systems (macOS and Linux), serial devices are accessed through files in the /dev/ directory. After the serial port is selected, the user must specify the settings for the port. Communication speed will vary with devices, but typical values are 9600, 19,200, and 115,200 bits per second. Once the ports are open for communication on both devices, it is possible to send and receive data.

    diff --git a/content/static/tutorials/gettingstarted/index.html b/content/static/tutorials/gettingstarted/index.html index 5def1e1a5..03dc218b3 100644 --- a/content/static/tutorials/gettingstarted/index.html +++ b/content/static/tutorials/gettingstarted/index.html @@ -17,7 +17,7 @@

    Casey Reas and Ben Fry

    the desktop, but the important thing is for the processing folder to be pulled out of that .zip file. Then double-click processing.exe to start. -
  • The Mac OS X version is also a .zip file. Double-click it and drag the Processing +
  • The macOS version is also a .zip file. Double-click it and drag the Processing icon to the Applications folder. If you're using someone else's machine and can't modify the Applications folder, just drag the application to the desktop. Then double-click the Processing icon to start.
    • diff --git a/content/static/tutorials/overview/index.html b/content/static/tutorials/overview/index.html index 8b9987eff..e5ca9cc6d 100644 --- a/content/static/tutorials/overview/index.html +++ b/content/static/tutorials/overview/index.html @@ -155,7 +155,7 @@

    Exporting and distributing your work

    - One of the most significant features of the Processing environment is its ability to bundle your sketch into an application with just one click. Select File → Export Application to package your current sketch as an application. This will bundle your sketch as an application for Windows, Mac OS X, or Linux depending on which operating system you're exporting from. The application folders are overwritten whenever you export—make a copy or remove them from the sketch folder before making changes to the contents of the folder. Alternatively, you can turn off the automatic file erasure in the Preferences. + One of the most significant features of the Processing environment is its ability to bundle your sketch into an application with just one click. Select File → Export Application to package your current sketch as an application. This will bundle your sketch as an application for Windows, macOS, or Linux depending on which operating system you're exporting from. The application folders are overwritten whenever you export—make a copy or remove them from the sketch folder before making changes to the contents of the folder. Alternatively, you can turn off the automatic file erasure in the Preferences.

    diff --git a/download/_downloads.php b/download/_downloads.php index 798bebf2f..ea5128625 100644 --- a/download/_downloads.php +++ b/download/_downloads.php @@ -1,7 +1,7 @@

    -

    Download Processing. Processing is available for Linux, Mac OS X, and Windows. Select your choice to download the software below.

    +

    Download Processing. Processing is available for Linux, macOS, and Windows. Select your choice to download the software below.

    Thank you for donating to the Processing Foundation.
    @@ -21,7 +21,7 @@
  • Linux 64-bit
    Linux 32-bit
    Linux ARMv6hf
    • -
  • Mac OS X
    • +
  • macOS
    • @@ -52,7 +52,7 @@ Linux 32 Linux 64 Linux ARMv6hf - Mac OS X + macOS
  • 3.2.2 @@ -62,7 +62,7 @@ Linux 32 Linux 64 Linux ARMv6hf - Mac OS X +
    • - diff --git a/content/api_en/displayDensity.xml b/content/api_en/displayDensity.xml index 5f2e71814..3e4e0ece1 100644 --- a/content/api_en/displayDensity.xml +++ b/content/api_en/displayDensity.xml @@ -26,7 +26,7 @@ void draw() { diff --git a/content/api_en/environment/index.html b/content/api_en/environment/index.html index 6fb7d771a..6d2d44fe6 100644 --- a/content/api_en/environment/index.html +++ b/content/api_en/environment/index.html @@ -135,10 +135,10 @@
    File
    Prints the code inside the text editor.
  • Preferences
    Change some of the ways Processing works. (This item is located in the Processing menu - on macOS.)
    • + on Mac.)
  • Quit
    Exits the Processing Environment and closes all Processing windows. (This item is - located in the Processing menu on macOS.)
    • + located in the Processing menu on Mac.)
    Edit
    @@ -278,7 +278,7 @@

    The Processing Development Environment (PDE) is highly configurable. The most common preferences can be modified in the Preferences window, located in the File menu on - Windows and Linux and in the Processing menu on macOS. The full list of preferences + Windows and Linux and in the Processing menu on Mac. The full list of preferences are stored in the "preferences.txt" file. This file can be opened and edited directly only when Processing is not running. You can find the location of this file on your computer by reading the bottom-left corner of the Preferences window. @@ -503,7 +503,7 @@

    Java Mode

    This mode makes it possible to write short programs to draw to the screen, but also enables complex Java programs as well. It can be used simply by beginners, but it scales to professional Java software development. Sketches written in this mode can - be exported as Java Applications to run on Linux, macOS, and Windows operating systems. + be exported as Java Applications to run on Linux, Mac, and Windows operating systems.

    diff --git a/content/api_en/launch.xml b/content/api_en/launch.xml index 36ca39280..44bf7f879 100755 --- a/content/api_en/launch.xml +++ b/content/api_en/launch.xml @@ -30,9 +30,9 @@ void mousePressed() { filename parameter is a String specifying the file name and location. The location parameter must be a full path name, or the name of an executable in the system's PATH. In most cases, using a full path is the best option, rather than relying on the system PATH. Be sure to make the file executable before attempting to open it (chmod +x).

    -This function (roughly) emulates what happens when you double-click an application or document in the macOS Finder, the Windows Explorer, or your favorite Linux file manager. If you're trying to run command line functions directly, use the exec() function instead (see below).
    +This function (roughly) emulates what happens when you double-click an application or document in the Mac Finder, the Windows Explorer, or your favorite Linux file manager. If you're trying to run command line functions directly, use the exec() function instead (see below).

    -This function behaves differently on each platform. On Windows, the parameters are sent to the Windows shell via "cmd /c". On macOS, the "open" command is used (type "man open" in Terminal.app for documentation). On Linux, it first tries gnome-open, then kde-open, but if neither are available, it sends the command to the shell and prays that something useful happens.
    +This function behaves differently on each platform. On Windows, the parameters are sent to the Windows shell via "cmd /c". On Mac, the "open" command is used (type "man open" in Terminal.app for documentation). On Linux, it first tries gnome-open, then kde-open, but if neither are available, it sends the command to the shell and prays that something useful happens.

    For users familiar with Java, this is not the same as Runtime.exec(), because the launcher command is prepended. Instead, the exec(String[]) function is a shortcut for Runtime.getRuntime.exec(String[]). The exec() function is documented in the     JavaDoc in the PApplet class. ]]> diff --git a/content/api_en/mouseWheel.xml b/content/api_en/mouseWheel.xml index 7fb0f1367..f1c00c32d 100755 --- a/content/api_en/mouseWheel.xml +++ b/content/api_en/mouseWheel.xml @@ -26,7 +26,7 @@ void mouseWheel(MouseEvent event) { mouseWheel() function returns positive values when the mouse wheel is rotated down (toward the user), and negative values for the other direction (up or away from the user). On macOS with "natural" scrolling enabled, the values are opposite. +The mouseWheel() function returns positive values when the mouse wheel is rotated down (toward the user), and negative values for the other direction (up or away from the user). On Mac with "natural" scrolling enabled, the values are opposite.

    Mouse and keyboard events only work when a program has draw(). Without draw(), the code is only run once and then stops listening for events. ]]>     diff --git a/content/api_en/pixelHeight.xml b/content/api_en/pixelHeight.xml index 03c6fc3be..73ced7bf9 100755 --- a/content/api_en/pixelHeight.xml +++ b/content/api_en/pixelHeight.xml @@ -16,7 +16,7 @@ println(pixelWidth, pixelHeight); pixelDensity(2) is used to make use of a high resolution display (called a Retina display on macOS or high-dpi on Windows and Linux), the width and height of the sketch do not change, but the number of pixels is doubled. As a result, all operations that use pixels (like loadPixels(), get(), set(), etc.) happen in this doubled space. As a convenience, the variables pixelWidth and pixelHeight hold the actual width and height of the sketch in pixels. This is useful for any sketch that uses the pixels[] array, for instance, because the number of elements in the array will be pixelWidth*pixelHeight, not width*height. +When pixelDensity(2) is used to make use of a high resolution display (called a Retina display on Mac or high-dpi on Windows and Linux), the width and height of the sketch do not change, but the number of pixels is doubled. As a result, all operations that use pixels (like loadPixels(), get(), set(), etc.) happen in this doubled space. As a convenience, the variables pixelWidth and pixelHeight hold the actual width and height of the sketch in pixels. This is useful for any sketch that uses the pixels[] array, for instance, because the number of elements in the array will be pixelWidth*pixelHeight, not width*height. ]]> \ No newline at end of file diff --git a/content/api_en/pixelWidth.xml b/content/api_en/pixelWidth.xml index de15f418b..28a077382 100755 --- a/content/api_en/pixelWidth.xml +++ b/content/api_en/pixelWidth.xml @@ -16,7 +16,7 @@ println(pixelWidth, pixelHeight); pixelDensity(2) is used to make use of a high resolution display (called a Retina display on macOS or high-dpi on Windows and Linux), the width and height of the sketch do not change, but the number of pixels is doubled. As a result, all operations that use pixels (like loadPixels(), get(), set(), etc.) happen in this doubled space. As a convenience, the variables pixelWidth and pixelHeight hold the actual width and height of the sketch in pixels. This is useful for any sketch that uses the pixels[] array, for instance, because the number of elements in the array will be pixelWidth*pixelHeight, not width*height. +When pixelDensity(2) is used to make use of a high resolution display (called a Retina display on Mac or high-dpi on Windows and Linux), the width and height of the sketch do not change, but the number of pixels is doubled. As a result, all operations that use pixels (like loadPixels(), get(), set(), etc.) happen in this doubled space. As a convenience, the variables pixelWidth and pixelHeight hold the actual width and height of the sketch in pixels. This is useful for any sketch that uses the pixels[] array, for instance, because the number of elements in the array will be pixelWidth*pixelHeight, not width*height. ]]> \ No newline at end of file diff --git a/content/api_en/size.xml b/content/api_en/size.xml index 50ddae1f3..c749dcda4 100755 --- a/content/api_en/size.xml +++ b/content/api_en/size.xml @@ -61,7 +61,7 @@ As of Processing 3, to run a sketch at the full dimensions of a screen, use the
    The maximum width and height is limited by your operating system, and is usually the width and height of your actual screen. On some machines it may simply be the number of pixels on your current screen, meaning that a screen of 800 x 600 could support size(1600, 300), since that is the same number of pixels. This varies widely, so you'll have to try different rendering modes and sizes until you get what you're looking for. If you need something larger, use createGraphics to create a non-visible drawing surface.

    -The minimum width and height is around 100 pixels in each direction. This is the smallest that is supported across Windows, macOS, and Linux. We enforce the minimum size so that sketches will run identically on different machines. +The minimum width and height is around 100 pixels in each direction. This is the smallest that is supported across Windows, Mac, and Linux. We enforce the minimum size so that sketches will run identically on different machines.
    The renderer parameter selects which rendering engine to use. For example, if you will be drawing 3D shapes, use P3D. In addition to the default renderer, other renderers are:

    diff --git a/content/static/tutorials/data/index.html b/content/static/tutorials/data/index.html index c5314dadd..e2cc5a468 100644 --- a/content/static/tutorials/data/index.html +++ b/content/static/tutorials/data/index.html @@ -183,7 +183,7 @@

    Working with Text Files

    - In order to create a text file, you can use any simple text editor. Windows Notepad or macOS TextEdit will do; just make sure you format the file as “plain text.” It is also advisable to name the text files with the “.txt” extension, to avoid any confusion. And just as with image files, these text files should be placed in the sketch’s “data” directory in order for them to be recognized by the Processing sketch.

    + In order to create a text file, you can use any simple text editor. Windows Notepad or Mac TextEdit will do; just make sure you format the file as “plain text.” It is also advisable to name the text files with the “.txt” extension, to avoid any confusion. And just as with image files, these text files should be placed in the sketch’s “data” directory in order for them to be recognized by the Processing sketch.

    Once the text file is in place, Processing’s loadStrings() function is used to read the content of the file into a String array. The individual lines of text in the file each become an individual element in the array. diff --git a/content/static/tutorials/eclipse/index.html b/content/static/tutorials/eclipse/index.html index 41c4e9fd9..c45095c4c 100644 --- a/content/static/tutorials/eclipse/index.html +++ b/content/static/tutorials/eclipse/index.html @@ -35,7 +35,7 @@

    The idea of Libraries

    Import the Processing Core

    In order for Eclipse to see the code that makes up Processing, we need to import it into our project.

    File > Import > General > File System

    -

    Click next. On Windows, click "Browse..." and select the Processing jar files inside PATH_TO_PROCESSING/core/library/. On macOS, do not use the "Browse..." button. Instead, use the "From directory:" field to manually enter the path to Processing's jar files, which is typically /Applications/Processing 3.app/Contents/Java/core/library/. At minimum, select the "core.jar" file inside the "library" folder.

    +

    Click next. On Windows, click "Browse..." and select the Processing jar files inside PATH_TO_PROCESSING/core/library/. On Mac, do not use the "Browse..." button. Instead, use the "From directory:" field to manually enter the path to Processing's jar files, which is typically /Applications/Processing 3.app/Contents/Java/core/library/. At minimum, select the "core.jar" file inside the "library" folder.

    Importing the Processing Core

    A .jar file is a compiled collection of Java code. The core.jar is the core of the Processing libraries, it has all the code that does the stuff that we are used to doing in Processing, like drawing shapes. Once we have it, we can make use of all the normal Processing commands that are found on the reference page.

    Click Finish. If you look at the Package Explorer, you'll notice that there is a new file in our project, called 'core.jar'.

    diff --git a/content/static/tutorials/electronics/index.html b/content/static/tutorials/electronics/index.html index 5d08d7afd..754e8f31c 100644 --- a/content/static/tutorials/electronics/index.html +++ b/content/static/tutorials/electronics/index.html @@ -273,7 +273,7 @@

    Sensors and communication

    - Because a device can have several serial ports, a user must specify which serial port to use for data transmission. On most Windows computers, serial port names are COMx, where x can be 1, 2, 3, etc. On UNIX-based systems (macOS and Linux), serial devices are accessed through files in the /dev/ directory. After the serial port is selected, the user must specify the settings for the port. Communication speed will vary with devices, but typical values are 9600, 19,200, and 115,200 bits per second. Once the ports are open for communication on both devices, it is possible to send and receive data. + Because a device can have several serial ports, a user must specify which serial port to use for data transmission. On most Windows computers, serial port names are COMx, where x can be 1, 2, 3, etc. On UNIX-based systems (Mac and Linux), serial devices are accessed through files in the /dev/ directory. After the serial port is selected, the user must specify the settings for the port. Communication speed will vary with devices, but typical values are 9600, 19,200, and 115,200 bits per second. Once the ports are open for communication on both devices, it is possible to send and receive data.

    diff --git a/content/static/tutorials/gettingstarted/index.html b/content/static/tutorials/gettingstarted/index.html index 03dc218b3..f5d1fbfec 100644 --- a/content/static/tutorials/gettingstarted/index.html +++ b/content/static/tutorials/gettingstarted/index.html @@ -17,7 +17,7 @@

    Casey Reas and Ben Fry

    the desktop, but the important thing is for the processing folder to be pulled out of that .zip file. Then double-click processing.exe to start. -
  • The macOS version is also a .zip file. Double-click it and drag the Processing +
  • The Mac version is also a .zip file. Double-click it and drag the Processing icon to the Applications folder. If you're using someone else's machine and can't modify the Applications folder, just drag the application to the desktop. Then double-click the Processing icon to start.
    • diff --git a/content/static/tutorials/overview/index.html b/content/static/tutorials/overview/index.html index e5ca9cc6d..0ffc85b20 100644 --- a/content/static/tutorials/overview/index.html +++ b/content/static/tutorials/overview/index.html @@ -155,7 +155,7 @@

    Exporting and distributing your work

    - One of the most significant features of the Processing environment is its ability to bundle your sketch into an application with just one click. Select File → Export Application to package your current sketch as an application. This will bundle your sketch as an application for Windows, macOS, or Linux depending on which operating system you're exporting from. The application folders are overwritten whenever you export—make a copy or remove them from the sketch folder before making changes to the contents of the folder. Alternatively, you can turn off the automatic file erasure in the Preferences. + One of the most significant features of the Processing environment is its ability to bundle your sketch into an application with just one click. Select File → Export Application to package your current sketch as an application. This will bundle your sketch as an application for Windows, Mac, or Linux depending on which operating system you're exporting from. The application folders are overwritten whenever you export—make a copy or remove them from the sketch folder before making changes to the contents of the folder. Alternatively, you can turn off the automatic file erasure in the Preferences.

    diff --git a/download/_downloads.php b/download/_downloads.php index ea5128625..5989233f2 100644 --- a/download/_downloads.php +++ b/download/_downloads.php @@ -1,7 +1,7 @@

    -

    Download Processing. Processing is available for Linux, macOS, and Windows. Select your choice to download the software below.

    +

    Download Processing. Processing is available for Linux, Mac, and Windows. Select your choice to download the software below.

    Thank you for donating to the Processing Foundation.
    @@ -21,7 +21,7 @@
  • Linux 64-bit
    Linux 32-bit
    Linux ARMv6hf
    • -
  • macOS
    • +
  • Mac
    • @@ -52,7 +52,7 @@ Linux 32 Linux 64 Linux ARMv6hf - macOS + Mac
  • 3.2.2 @@ -62,7 +62,7 @@ Linux 32 Linux 64 Linux ARMv6hf - +