Disclaimer: this is obviously to my aesthetic taste, a kind of tobyspark barebones default.
What's important: This clarifies the data and event handling of the graph. It communicates what is going on better, using fewer concepts. Execution aka events is the two pixel black line. Nodes are outlined in this -- they execute! -- and any port data or patch cable touching this will gain the 2px line and transmit events. If data ports transmit events, they touch the node. If they don't, they're held slightly away from the node; an insulation gap.
I haven't addressed port doors. You could do a graphic something, but I'd suggest not rendering doors as doors rather than the actual state of the port -- wall or not, as defined by ie. the select input -- fails your goal of no mystery meat.
Look at interacts with environment node. Wonder why a centimeter of my screen is taken up with huge curved lines.
It's lost any semiotic value it might have had as a compact wi-fi / airport like icon.
it's hugely inefficient space-wise, taking up lots of valuable patching real-estate.
Look at stateful node. Wonder what the meaning of that strange line on the bottom is again.
no semiotic value at all.
Suggest working these into compact icons in the title bar. Overall, I think the node design could do a little more work -- too big, to start with. Rapidly run out of space on a laptop screen (15" even), and it makes it hard to get an overview of the patch's workings. If the editor were open source, I might have tried some tweaks myself.
The ability to change the Editor window background color and opacity would make a great workflow improvement and allow you to view the changes you are making whilst still having the Editor at full size.
Is a Inspector window in the pipeline that would allow us to select a object and enter values.
For example with the Make 3D point node i have to clikc on each port individually to change the values. Would be great to have a inspector window so you could quickly tab through the values and adjust them.
Hey there, thanks for checking out Vuo. I'm Travis; in this tutorial we'll create a composition that utilizes a feedback loop in order to count upward. This is our composition in complete form (all nodes linked together), and this is our feedback loop (between Hold Value node and Add node). First we'll run this composition and get a visual for what it creates, we'll walk through what some of the nodes perform in the composition, then we'll delete it and build the composition together, step by step. So let's go ahead and run it (click "Run" button).