-
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Jayson Haebich
authored and
Jayson Haebich
committed
Jan 12, 2023
1 parent
406b44a
commit 4ae599a
Showing
1 changed file
with
41 additions
and
105 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,120 +1,56 @@ | ||
| The following describes how to set up a Processing Library project in Eclipse and build it successfully, and to make your Library ready for distribution. | ||
| ___ __ ____ __ ____ ___ ___ ________________________ | ||
| / _ \/ |/ / |/_/ / / / / _ | / _ \/_ __/ _/ __/_ __/ __/ | ||
| / // / /|_/ /> < /_ _/ / __ |/ , _/ / / _/ /_\ \ / / _\ \ | ||
| /____/_/ /_/_/|_| /_/ /_/ |_/_/|_| /_/ /___/___/ /_/ /___/ | ||
| # Introduction | ||
| This is a processing library to control generic FTDI DMX USB devices, such as the Enttec Open DMX device. The library is designed to be as easy to use as possible for people | ||
| that are new to programming and DMX lighting. It includes methods and classes for creating timelines, oscilators, trigger events and other behaviours to make it easy to control | ||
| your DMX based lighting fixtures. | ||
|
|
||
| ## Import to Eclipse | ||
| This library has been tested and works with both Windows and OSX. It is designed to be used with generic FTDI DMX USB devices which are commonly found in the cheap usb DMX | ||
| controllers you see on Taobao and Aliexpress. | ||
|
|
||
| There are three options to import the template project into Eclipse: using it as a template, using a Git [fork](https://help.github.com/articles/fork-a-repo) or using a downloaded package. If you are not familiar with Git or GitHub, you should opt for the downloaded package. | ||
|  | ||
|
|
||
| ### Option A: Use this template | ||
| ## Version | ||
| The latest version of this library 1.5 has been updated to work with Processing 4 (yay!) | ||
|
|
||
| 1. Use the repository as a template. | ||
| * Navigate to https://github.com/processing/processing-library-template in your browser. | ||
| * Click the "Use this template" button in the top-right of the page. | ||
| * Your repository name will be your Library name. | ||
| 1. Clone your new repository to your Eclipse workspace. | ||
| * Open Eclipse and select the File → Import... menu item. | ||
| * Select Git → Projects from Git, and click "Next >". | ||
| * Select "URI" and click "Next >". | ||
| * Enter your repository's clone URL in the "URI" field. The remaining fields in the "Location" and "Connection" groups will get automatically filled in. | ||
| * Enter your GitHub credentials in the "Authentication" group, and click "Next >". | ||
| * Select the `master` branch on the next screen, and click "Next >". | ||
| * The default settings on the "Local Configuration" screen should work fine, click "Next >". | ||
| * Make sure "Import existing projects" is selected, and click "Next >". | ||
| * Eclipse should find and select the `processing-library-template` automatically, click "Finish". | ||
| 1. Rename your Eclipse project. | ||
| * In the Package Explorer, right-click (ctrl-click) on the folder icon of the `processing-library-template` project, and select Refactor → Rename... from the menu that pops up. | ||
| * Give the project the name of your Library, and click "OK". | ||
|
|
||
| ### Option B: GitHub | ||
| ## Setting up | ||
|
|
||
| 1. Fork the template repository to use as a starting point. | ||
| * Navigate to https://github.com/processing/processing-library-template in your browser. | ||
| * Click the "Fork" button in the top-right of the page. | ||
| * Once your fork is ready, open the new repository's "Settings" by clicking the link in the menu bar on the right. | ||
| * Change the repository name to the name of your Library and save your changes. | ||
| * NOTE: GitHub only allows you to fork a project once. If you need to create multiple forks, you can follow these [instructions](https://beeznest.wordpress.com/2013/12/26/creating-multiple-forks-using-upstream-branches/). | ||
| 1. Clone your new repository to your Eclipse workspace. | ||
| * Open Eclipse and select the File → Import... menu item. | ||
| * Select Git → Projects from Git, and click "Next >". | ||
| * Select "URI" and click "Next >". | ||
| * Enter your repository's clone URL in the "URI" field. The remaining fields in the "Location" and "Connection" groups will get automatically filled in. | ||
| * Enter your GitHub credentials in the "Authentication" group, and click "Next >". | ||
| * Select the `master` branch on the next screen, and click "Next >". | ||
| * The default settings on the "Local Configuration" screen should work fine, click "Next >". | ||
| * Make sure "Import existing projects" is selected, and click "Next >". | ||
| * Eclipse should find and select the `processing-library-template` automatically, click "Finish". | ||
| 1. Rename your Eclipse project. | ||
| * In the Package Explorer, right-click (ctrl-click) on the folder icon of the `processing-library-template` project, and select Refactor → Rename... from the menu that pops up. | ||
| * Give the project the name of your Library, and click "OK". | ||
|
|
||
| ### Option C: Downloaded Package | ||
| The library should now run straight away without any configuration. But if you are having problems please follow the steps below: | ||
|
|
||
| 1. Download the latest Eclipse template from [here](https://github.com/processing/processing-library-template/releases). **Don't unzip the ZIP file yet.** | ||
| 1. Create a new Java project in Eclipse. | ||
| * From the menubar choose File → New → Java Project. | ||
| * Give the project the name of your Library. | ||
| * Click "Finish". | ||
| 1. Import the template source files. | ||
| * Right-click (ctrl-click) onto the folder icon of your newly created project in the Package Explorer and select "Import..." from the menu that pops up. | ||
| * Select General → Archive File, and click "Next >". | ||
| * Navigate to the ZIP file you downloaded earlier in step 1, and click "Finish". | ||
| ### OSX | ||
| 1. Copy the libftd2xx.1.2.2.dylib in the dependencies folder to /usr/local/lib folder (requires sudo) | ||
| 2. Set the permissions for symlink: sudo chmod a+r /usr/local/lib/libftd2xx.1.2.2.dylib | ||
| 3. Create a symlink: sudo ln -sf /usr/local/lib/libftd2xx.1.2.2.dylib /usr/local/lib/libftd2xx.dylib | ||
| 4. Set the permissions for symlink: sudo chmod a+r /usr/local/lib/libftd2xx.dylib | ||
| 5. Check that the AppleFTDI driver is not enabled: sudo kextunload -b com.apple.driver.AppleUSBFTDI | ||
|
|
||
| ## Set Up and Compile | ||
| ### Windows | ||
|
|
||
| 1. Add Processing to the project build path. | ||
| * Open your project's "Properties" window. | ||
| * Under "Java Build Path", select the "Libraries" tab and then "Add External JARs...". | ||
| * Locate and add Processing's `core.jar` to your build path. It is recommended that a copy of `core.jar` is located in your Eclipse workspace in a `libs` folder. If the `libs` folder does not exist yet, create it. Read the [section below](#AddingJARs) regarding where to find the `core.jar` file. | ||
| * Confirm the setup with "OK". | ||
| 1. Edit the Library properties. | ||
| * Open the `resources` folder inside of your Java project and double-click the `build.properties` file. You should see its contents in the Eclipse editor. | ||
| * Edit the properties file, making changes to items 1-4 so that the values and paths are properly set for your project to compile. A path can be relative or absolute. | ||
| * Make changes to items under 5. These are metadata used in the automatically generated HTML, README, and properties documents. | ||
| 1. Compile your Library using Ant. | ||
| * From the menu bar, choose Window → Show View → Ant. A tab with the title "Ant" will pop up on the right side of your Eclipse editor. | ||
| * Drag the `resources/build.xml` file in there, and a new item "ProcessingLibs" will appear. | ||
| * Press the "Play" button inside the "Ant" tab. | ||
| 1. BUILD SUCCESSFUL. The Library template will start to compile, control messages will appear in the console window, warnings can be ignored. When finished it should say BUILD SUCCESSFUL. Congratulations, you are set and you can start writing your own Library by making changes to the source code in folder `src`. | ||
| 1. BUILD FAILED. In case the compile process fails, check the output in the console which will give you a closer idea of what went wrong. Errors may have been caused by | ||
| * Incorrect path settings in the `build.properties` file. | ||
| * Error "Javadoc failed". if you are on Windows, make sure you are using a JDK instead of a JRE in order to be able to create the Javadoc for your Library. JRE does not come with the Javadoc application, but it is required to create Libraries from this template. | ||
| Put the ftd2xx.dll file in the dependencies/win folder into your C:/windows/system32 folder | ||
|
|
||
| After having compiled and built your project successfully, you should be able to find your Library in Processing's sketchbook folder, examples will be listed in Processing's sketchbook menu. Files that have been created for the distribution of the Library are located in your Eclipse's `workspace/yourProject/distribution` folder. In there you will also find the `web` folder which contains the documentation, a ZIP file for downloading your Library, a folder with examples as well as the `index.html` and CSS file. | ||
| ### Still having problems? | ||
|
|
||
| To distribute your Library please refer to the [Library Guidelines](https://github.com/processing/processing/wiki/Library-Guidelines). | ||
| Try installing qlc plus https://qlcplus.org/ which may set up some extra system properties that need to be set | ||
|
|
||
| ## Source code | ||
| ## | ||
|
|
||
| If you want to share your Library's source code, we recommend using an online repository available for free at [GitHub](https://github.com/). | ||
|
|
||
| ## <a name='AddingJARs'/>Adding core.jar and other .jar files to your classpath</a> | ||
| This library was create for the DMX Lighting for Artists workshop for OFCourse in Shanghai, that was run in 2019. Credit to Omar Khan whose code helped me to understand how to | ||
| interface with FTDI device https://github.com/orcaomar | ||
|
|
||
| The `core.jar` file contains the core classes of Processing and has to be part of your classpath when building a Library. On Windows and Linux, this file is located in the Processing distribution folder inside a folder named `lib`. On Mac OS X, right-click the Processing.app and use "Show Package Contents" to see the guts. The `core.jar` file is inside Contents → Resources → Java. For further information about the classes in `core.jar`, you can see the source [here](http://code.google.com/p/processing/source/browse/trunk/processing#processing/core) and the developer documentation [here](http://processing.googlecode.com/svn/trunk/processing/build/javadoc/core/index.html). | ||
| _.-~ ) | ||
| _..--~~~~,' ,-/ _ ((visit ofcourse.io)) | ||
| .-'. . . .' ,-',' ,' ) | ||
| ,'. . . _ ,--~,-'__..-' ,' | ||
| ,'. . . (@)' ---~~~~ ,' | ||
| /. . . . '~~ ,-' | ||
| /. . . . . ,-' | ||
| ; . . . . - . ,' | ||
| : . . . . _ / | ||
| . . . . . `-.: | ||
| . . . ./ - . ) | ||
| . . . | _____..---.._/ | ||
|
|
||
| If you created a `libs` folder as described above, put the libraries you need to add to your classpath in there. In the "Properties" of your Java project, navigate to Java Build Path → Libraries, and click "Add External JARs...". Select the `.jar` files from the `libs` folder that are required for compiling your project. Adjust the `build.xml` file accordingly. | ||
|
|
||
| The `libs` folder is recommended but not a requirement, nevertheless you need to specify where your `.jar` files are located in your system in order to add them to the classpath. | ||
|
|
||
| In case a Library depends on system libraries, put these dependencies next to the `.jar` file. For example, Processing's `opengl.jar` Library depends on JOGL hence the DLLs (for Windows) or jnilibs (for OS X) have to be located next to the `opengl.jar` file. | ||
|
|
||
| ## What is the difference between JDK and JRE? | ||
|
|
||
| JDK stands for Java Development Kit whereas JRE stands for Java Runtime Environment. For developers it is recommended to work with a JDK instead of a JRE since more Java development related applications such as Javadoc are included. Javadoc is a requirement to properly compile and document a Processing Library as described on the guidelines page. | ||
|
|
||
| You can have both a JDK and a JRE installed on your system. In Eclipse you need to specify which one you want to use. | ||
|
|
||
| ## The JRE System Library | ||
|
|
||
| This primarily affects Windows and Linux users (because the full JDK is installed by default on Mac OS X). It is recommended that you use the JDK instead of a JRE. The JDK can be downloaded from [Oracle's download site](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Also see the [Java Platform Installation page](http://www.oracle.com/technetwork/java/javase/index-137561.html), which contains useful information. | ||
|
|
||
| To change the JRE used to compile your Java project: | ||
|
|
||
| 1. Open the properties of your project from the menu Project → Properties. Select "Java Build Path" and in its submenu, click on the "Libraries" tab. | ||
| 1. A list of JARs and class folders in the build path will show up. In this list you can find the JRE System Library that is used to compile your code. Remove this JRE System library. | ||
| 1. Click "Add Library...". In the popup window, choose "JRE System Library" and press "Next". | ||
| 1. Select an alternate JRE from the pull-down menu or click and modify the "Installed JREs". Confirm with "Finish" and "OK". | ||
|
|
||
| ## Compiling with Ant and javadoc | ||
|
|
||
| Ant is a Java-based build tool. For [more information](http://ant.apache.org/faq.html#what-is-ant) visit the [Ant web site](http://ant.apache.org/). Ant uses a file named `build.xml` to store build settings for a project. | ||
|
|
||
| Javadoc is an application that creates an HTML-based API documentation of Java code. You can check for its existence by typing `javadoc` on the command line. On Mac OS X, it is installed by default. On Windows and Linux, installing the JDK will also install the Javadoc tool. |