mixing code, visual reference materials, running instances, and data in the same space (I explored some of these ideas in Protoboard)
VPLs, understood as "nodes-and-wires", usually provide some sort of infinite canvas to lay functions on, I'm curious if this combination is necessary - can the code still be text (or some other structural approach), while I can still "keep some functions here on the right of that other thing" - basically thinking spatially about my code
notable work in this direction is Dark ↗ (also featuring the "embodied data" idea):
taking this even further, is using the spatiality for semantic - executing code spatially - Neighbour Computing note says more about this