More Information

We will be fixing bugs and adding features in the core Processing source code, the Processing Development Environment. We'll also be working on integrating Processing with Eclipse, VIM, Emacs, TextMate, etc, and hacking on things based on Processing such as Ruby-Processing and Processing.js.

If you aren't a programmer, you can contribute too by creating a sketch with Processing and letting people know how awesome it is.

For more information about Processing, visit http://processing.org/

Tasks, Features, Bugs

Processing: Core & Libraries

Thanks to Ben Fry and Casey Reas for Processing

Working on the code

Important: If you are going to work on the core or library code base for Processing, you can download or check out the code from two different places:

1. the official Processing.org source code repo requiring Subversion and found here:
   http://dev.processing.org/source/index.cgi/trunk/processing/
2. the minor fork OhProcessing source code repo requiring git and found here:
   http://github.com/omouse/ohprocessing/tree/master

Find out more about the differences between them.

Bugs/Tasks

• Finishing the command-line support (preferences.txt support is missing) and perhaps including some more options.
• Fix the troubles users with non-ASCII characters in their name are having.
• Out of memory error when using ellipse() with OpenGL.

Click here to find more bugs to fix!

for derivative implementations

Derivative implementations of Processing are programs that do the same things as Processing. You type in the same Processing commands but in a different programming language and the result is the same. The advantage is that this other programming language may have features that Processing doesn't have.

Ruby-Processing

Thanks to Jeremy Ashkenas for this list.

• Finish converting the Learning Processing book sketches over to idiomatic Ruby. This is about half done now.
• Look through the processing docs/source and write specs to ensure that the Processing methods are 100% available from Ruby.
• Finish off the specs for ruby_processing.rb
• Refactor the script/watch, script/open, script/live, script/generate, script/applet, and script/application commands into a single executable, which could be installed in the user's path, so you could do something like: ruby-processing open.
• Create a TextMate bundle that gives you access to the above commands.
• Make pretty sketches and contribute them to the samples folder.

Clojure-Processing

Thanks to Roland Sadowski for this list.

• making it easier to use Clojure+Processing: right now you have to use proxies or gen-class to use PApplet. It would be nice if the user could just create a script with functions 'setup' and 'draw' etc, like in regular Processing code.
• adding doc strings to functions so using the library from the REPL would be easier. This amounts to copy & pasting Processing documentation and abbreviating it.

for Text Editor Integeration

Text editor modes allow you to write Processing sketches in your favourite text editor rather than using the Processing Development Environment. Some of these modes are incomplete.

Emacs mode

• there is a bug in the compilation because the Commander class of Processing does not accept the --preferences option.
• the rest of the key bindings need to be added and checked to make sure that Processing does the right thing