Skip to content Skip to sidebar Skip to footer

What Is It That Stops Processings Libraries From Being Used To Processing.js

For those that don't know, processing is a language/ Java library primarily used for displaying data nice and pretty. Processing.js is its javascript port made by John Resiq. Every

Solution 1:

Processing.js and Processing may look similar, but obviously there are differences.

AFAIK Processing was made to make the life of designers/artists wanting to extend they're toolset via programming easier. Originally it was built as a Java library and a minimal IDE (the PDE). Processing.js is a port of that library in javascript.

This means that while to the user, Processing and Processing.js may look the same, behind the scenes the implementation is very different. As different as Java is to Javascript actually :)

To understand why Processing libraries won't work in Processing.js is to understand the differences between Java and Javascript. For example, javascript is a scripting language interpreted by the browser, while java code get's compiled into bytecode that is then executed by a virtual machine (the Java Virtual Machine (JVM)).

In conclusion, you can not use a Processing library (which is a Java library) with Processing.js, but you can port a Processing library from Java to Javascript if you want to. Toxiclibs.js is great example of that.

toxiclibs1toxiclibs2toxiclibs3

Post a Comment for "What Is It That Stops Processings Libraries From Being Used To Processing.js"