|
1 | | -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. |
| 1 | +Eliza is a port as a Processing library of the Java implementation of the Eliza program by Charles Hayden. |
| 2 | +Hayden's code is a complete and faithful implementation of the original program described by by Joseph Weizenbaum in Communications of the ACM in January 1966. |
2 | 3 |
|
3 | | -## Import to Eclipse |
| 4 | +ACKNOWLEDGMENTS |
4 | 5 |
|
5 | | -There are two options to import the template project into Eclipse: 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. |
| 6 | +1) Charles Hayden's Java implementation of Eliza: |
| 7 | +http://chayden.net/eliza/Eliza.html |
6 | 8 |
|
7 | | -### Option A: GitHub |
| 9 | +2) Processing Library Template: |
| 10 | +https://github.com/processing/processing-library-template |
8 | 11 |
|
9 | | -1. Fork the template repository to use as a starting point. |
10 | | - * Navigate to https://github.com/processing/processing-library-template in your browser. |
11 | | - * Click the "Fork" button in the top-right of the page. |
12 | | - * Once your fork is ready, open the new repository's "Settings" by clicking the link in the menu bar on the right. |
13 | | - * Change the repository name to the name of your library and save your changes. |
14 | | - * NOTE: GitHub only allows you to fork a project once. If you need to create multiple forks, you can follow these [instructions](http://adrianshort.org/2011/11/08/create-multiple-forks-of-a-github-repo/). |
15 | | -1. Clone your new repository to your Eclipse workspace. |
16 | | - * Open Eclipse and select the File → Import... menu item. |
17 | | - * Select Git → Projects from Git, and click "Next >". |
18 | | - * Select "URI" and click "Next >". |
19 | | - * Enter your repository's clone URL in the "URI" field. The remaining fields in the "Location" and "Connection" groups will get automatically filled in. |
20 | | - * Enter your GitHub credentials in the "Authentication" group, and click "Next >". |
21 | | - * Select the `master` branch on the next screen, and click "Next >". |
22 | | - * The default settings on the "Local Configuration" screen should work fine, click "Next >". |
23 | | - * Make sure "Import existing projects" is selected, and click "Next >". |
24 | | - * Eclipse should find and select the `processing-library-template` automatically, click "Finish". |
25 | | -1. Rename your Eclipse project. |
26 | | - * 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. |
27 | | - * Give the project the name of your library, and click "OK". |
28 | | - |
29 | | -### Option B: Downloaded Package |
| 12 | +INSTRUCTIONS |
30 | 13 |
|
31 | | -1. Download the latest Eclipse template from [here](https://github.com/processing/processing-library-template/releases). **Don't unzip the ZIP file yet.** |
32 | | -1. Create a new Java project in Eclipse. |
33 | | - * From the menubar choose File → New → Java Project. |
34 | | - * Give the project the name of your library. |
35 | | - * Click "Finish". |
36 | | -1. Import the template source files. |
37 | | - * 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. |
38 | | - * Select General → Archive File, and click "Next >". |
39 | | - * Navigate to the ZIP file you downloaded earlier in step 1, and click "Finish". |
| 14 | +The library is easy to use. Just import it, and then create an Eliza object: |
40 | 15 |
|
41 | | -## Set Up and Compile |
| 16 | +import codeanticode.eliza.*; |
42 | 17 |
|
43 | | -1. Add Processing to the project build path. |
44 | | - * Open your project's "Properties" window. |
45 | | - * Under "Java Build Path", select the "Libraries" tab and then "Add External JARs...". |
46 | | - * 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. |
47 | | - * Confirm the setup with "OK". |
48 | | -1. Edit the library properties. |
49 | | - * 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. |
50 | | - * 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. |
51 | | - * Make changes to items under 5. These are metadata used in the automatically generated HTML, README, and properties documents. |
52 | | -1. Compile your library using Ant. |
53 | | - * 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. |
54 | | - * Drag the `resources/build.xml` file in there, and a new item "ProcessingLibs" will appear. |
55 | | - * Press the "Play" button inside the "Ant" tab. |
56 | | -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`. |
57 | | -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 |
58 | | - * Incorrect path settings in the `build.properties` file. |
59 | | - * 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. |
| 18 | +```java |
| 19 | +Eliza eliza; |
| 20 | +eliza = new Eliza(this); |
60 | 21 |
|
61 | | -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. |
| 22 | +String response = eliza.processInput(“Hello”); |
| 23 | +println(response); |
| 24 | +``` |
62 | 25 |
|
63 | | -To distribute your library please refer to the [Library Guidelines](https://github.com/processing/processing/wiki/Library-Guidelines). |
| 26 | +You can use the readScript() function to change the script that Eliza uses to construct its answers: |
64 | 27 |
|
65 | | -## Source code |
| 28 | +```java |
| 29 | +eliza.readScript(“script”); |
| 30 | +eliza.readScript(“http://chayden.net/eliza/script"); |
| 31 | +``` |
66 | 32 |
|
67 | | -If you want to share your library's source code, we recommend using an online repository available for free at [Google Code] (http://code.google.com) or [GitHub](https://github.com/). |
| 33 | +To go back to the default script that is loaded when Eliza is initialized, call the readDefaultScript() function. |
68 | 34 |
|
69 | | -## <a name='AddingJARs'/>Adding core.jar and other .jar files to your classpath</a> |
| 35 | +http://chayden.net/eliza/instructions.txt |
70 | 36 |
|
71 | | -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). |
| 37 | +FURTHER REFERENCES |
72 | 38 |
|
73 | | -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. |
| 39 | +1) Wikipedia article about Eliza: http://en.wikipedia.org/wiki/ELIZA |
74 | 40 |
|
75 | | -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. |
76 | | - |
77 | | -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. |
78 | | - |
79 | | -## What is the difference between JDK and JRE? |
80 | | - |
81 | | -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. |
82 | | - |
83 | | -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. |
84 | | - |
85 | | -## The JRE System Library |
86 | | - |
87 | | -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. |
88 | | - |
89 | | -To change the JRE used to compile your Java project: |
90 | | - |
91 | | -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. |
92 | | -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. |
93 | | -1. Click "Add Library...". In the popup window, choose "JRE System Library" and press "Next". |
94 | | -1. Select an alternate JRE from the pull-down menu or click and modify the "Installed JREs". Confirm with "Finish" and "OK". |
95 | | - |
96 | | -## Compiling with Ant and javadoc |
97 | | - |
98 | | -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. |
99 | | - |
100 | | -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. |
| 41 | +2) Article from the Jul-Aug 1977 issue of the Creative Computing magazine, with a complete listing in Altair BASIC of a version of Eliza by Jeff Schrager: |
| 42 | +http://vintagecomputer.net/cisc367/Creative%20Computing%20Jul-Aug%201977%20Eliza%20BASIC%20listing.pdf |
0 commit comments