Toxiclibsjs v0.1.0
One year ago, I began porting a couple classes from Toxiclibs over to JavaScript. Now with 90 classes ported and several more nearly completed, Toxiclibsjs is beginning to take shape.
As of today, Toxiclibsjs is being built to the AMD API. It can be used with RequireJS, Node.js or the common way of a single global object as before. Being available in this manner means that not only is Toxiclibsjs available for the same uses as before, but now it can be used on the server-side and with desktop-based javascript programming environments such as Plask.
If you would like to use toxiclibsjs within Node.js it is now available on NPM and can be installed easily:
$ npm install toxiclibsjs
Along with this progress there are now several new classes:
- toxi.math.noise.PerlinNoise
- toxi.math.noise.simplexNoise
- toxi.math.conversion.unitTranslator
- toxi.processing.ToxiclibsSupport
- toxi.THREE.ToxiclibsSupport
Toxiclibsjs now follows the same package structure as the original Toxiclibs. So, if you previously used toxi.Vec2D, now you would use toxi.geom.Vec2D and this is consistent with all documentation for the original library. This can have a positive impact on users of both Processing and Processing.js because now you can refer to your toxiclibs class in long-form and in many more scenarios it will work without altering your code. Along these same objectives, one of the new classes that has been added is toxi.processing.ToxiclibsSupport this class, available in both versions will also ease moving between environments.
Since the release of Toxiclibsjs, I have tracked down several examples of its use on the internet, such as Mary Huang‘s Sake set Creator for Shapeways and Greg Kepler‘s Spider Web generator. I have also used it several of my own projects, such as our studio site for KVS Studio and sketches such as this Simplex Trails sketch I did recently.
Progress is being made to follow the path that Karsten Schmidt has set in his post The Road Ahead. There is now more documentation in the github repository. I will continue to be improving documentation and will be providing unit tests in the future.
Here are some links to the pieces mentioned as well as the new examples on the site:







Let's Get in Touch