Free tools like Processing and OpenFrameworks have provided elegant, quick coding for live graphics, but their interfaces have tended to be code-based. One exception has been the Mac-based Field, which provides graphical patching. Now, you can add NodeBox to that list. This free graphical creation toolkit, built on Python, had long allowed tinkering with and exporting beautiful illustrations, but its interface used code exclusively – and it ran on Macs only. Now, NodeBox 2, in an actively-developed beta, runs on Windows and adds a graphical patching interface.
The “Core Vector” Nodes act as much as a set of macros as anything, with basic objects for shapes, grids, lines, curves, and text paths – a bit like what you’d find in the toolbox of a graphical editing package.
Windows support is a good thing for PC users, but the terrific Digital Tools blog asks an interesting question – is adding more necessarily a good thing?
I just played with it a little bit, and can confirm, that this approach really leads to once again much quicker results, than tinkering with code only … [though] tinkering with code only is also an option
… I am totally in love with this plain simplicity of NodeBox1. Having too much of everything, and getting results too quickly is not always for the best.
NodeBox 2: Things are getting modular [Digital Tools]
It’s a reasonable point. After all, an environment like Processing could easily enough add this sort of patching interface – but sometimes, focusing on code, and even adjusting code, then running the results, can be more productive. And by resisting such functionality, Processing remains lightweight and easier to support.
On the other hand, modular patching can be a powerful interface metaphor.
NodeBox remains one to watch. It’s still not suitable for live visuals, animation, and interaction as are other environments, but it could offer lessons for those tools. And it remains a fascinating way to produce illustrations and designs.
