It's been quite a while since I last used Processing, having moved on to working in plain Java, but it was really useful and important to me when I was first learning ...
Fast forward to 2011, and I'm currently working on a cross-media patcher-style application in Java called Praxis (http://code.google.com/p/praxis/). I love patcher-style environments, though one of the downsides is obviously when the built-in components don't offer what you want(!), hence Praxis has live-coding possibilities built in as well. The Processing API was an obvious choice given it's quick and easy to work with, and people know it. This is a reimplementation though as it's built on top of Praxis' rendering pipeline.
It's new and under heavy development, so it's missing some better documentation, and there's some major omissions at the moment (transforms, text, etc.) as well as some things that work differently dues to the constraints of the environment and/or the fact that it's pure Java not Processing syntax. It also has a couple of extras (mainly blendMode() and animatable parameters).
There's a few examples on the code site, and I'll get on with adding documentation soon. I'll keep an eye on this thread if anyone's got any questions, or post the first question on Praxis' new discussion group!
Hope that's of interest to some of you. To the rest, apologies for the diversion, spam, etc
A quick update of this thread to say that a new release of Praxis LIVE has just been put up which brings the start of an OpenGL based rendering pipeline, alongside many other improvements. The Processing code support is still partial at the moment, though I've managed to run various sketches off OpenProcessing with no / minimal changes. Support will improve as Praxis moves into beta stage over the next few months.
The latest release of Praxis brings a range of new features, including the ability to live code control of audio, and a live code GLSL fragment shaders. More info here.
At some point soon I'll also post a blog about using Praxis from a Processing perspective and some of the differences. Praxis is not aimed at competing with Processing - it offers a different set of features for different use cases.
Best wishes, Neil
PS. This section used to be about Processing re-implementations, so I'm not sure if this thread still belongs in here or not? Praxis is written in Java, but the Processing support is mostly written from scratch.
This section has been renamed because of too many confusion from the users. It is much better now. But I would rather have named it Processing in Other Languages, as it is indeed more about rewriting Processing in... other languages. Well, including Java, too!
Wrote a blog post about Praxis' core architecture and the influence of the actor model. Might be of interest to people wondering where Praxis might be of use in comparison to using standard Processing. It's also got a few facts of more general use when working with multiple media.