Recently I've been looking at Povray, pyprocessing, and cfdg (version 3.0) as tools for creating digital images. I have branched two separate blogs where I mainly explore jruby + processing and processing.py

Sunday, 27 October 2013

Toxiclibs for the future

Some weeks back on the old processing discussion board, someone asked if he could he still use toxiclibs with the current version of processing. I have always found I could but then I've usually built latest version from source. Just clone the latest source, cd to the ant directory,
ant -f build-all.xml
and your done, pick up the zip file from the dist folder and unzip it in your libraries directory. You might want to move the libraries to the outer folder as well.
Further I've always modified the individual build scripts to use jdk level 1.6 changing.
<property name="lib.jdk.level" value="1.5"/>
to
<property name="lib.jdk.level" value="1.6"/>

In preparation for processing-2.1 I tried the following:-
<property name="lib.jdk.level" value="1.5"/>
to
<property name="lib.jdk.level" value="1.7"/>
I found I could successfully build against the latest development core.jar (compiled with jdk7), and toxiclibs runs just fine (and only minor adjustments are needed to run examples, mainly to do with obsoleted OPENGL calls or the need to import iterator). Thus toxiclibs appears to pretty much future proof already, I am looking forward to using java-8 in the near future (particularly with ruby-processing, which should benefit from various changes to the jvm), it would not do, to be stuck with jdk level 1.6 let alone jdk level 1.5 for that matter.

Followers

Blog Archive

About Me

My photo
Pembrokeshire, United Kingdom
I have developed JRubyArt and propane new versions of ruby-processing for JRuby-9.1.5.0 and processing-3.2.2