Dorian Zgraggen
Presented at the 12th Workshop on Live Programming (LIVE 2026). https://doi.org/10.5281/zenodo.24408560
Node-based programming is usually done on a two-dimensional canvas. What if it were done in a three-dimensional space? Spatial Nodes is a visual programming language for creative coding in virtual reality that tries to answer this question. Users can build interactive and animated worlds by connecting and manipulating nodes directly with their hands. The nodes are evaluated as the user modifies them, so the result of the user's action is visible on the scene in real time. The project shows how programming can become a spatial and embodied activity. It identifies some challenges in creating this kind of a programming environment, such as interaction design and debugging, and suggests that example scenes can be an effective way of learning how to use it.
https://www.dorianzgraggen.com/external/live2026Programming with your hands in a three-dimensional space is fun. It’s also fun to create scenes that react to your body and I think it makes sense to create such environments in the same environment they will be experienced in.
cables.gl is a similar project where you draw scenes using nodes. But cables.gl is trigger based: It has a main loop node with a trigger that runs decending nodes every frame. In Spatial Nodes, this is less explicit. Nodes run every frame by default as long as they're connected to an output node or are being preview by the user.
Redstone in Minecraft feels a bit similar, because players are also laying out programs in a three-dimensional space. In Minecraft, it feels more situated compared to my project, probably because in Spatial Nodes you can move, rotate and scale the node tree and they are placed in a dark void instead of next to grass blocks or trees.
There are a lot of things that could be designed and implemented to improve the usability of Spatial Nodes. For example, the project doesn't yet support any form of grouping nodes or defining and using functions. How would that work?
At the moment, nodes only support one output. Imagine a node where you can get the position and rotation of each individual joint of both hands. With the current system, i'd have to create two nodes for every joint. It would be much better to have a node that displays a hand and output sockets that are part of the displayed hand model.
Some test users reported that connecting and disconnecting nodes feels finicky. They can also reach situations that are tricky to exit, like when they draw a cube on their hands and then can't see their own fingers anymore.