• First Item
• Last Item
• Random Item
• And I guess when the "Allow List To Single Ports" will be implemented, the team will probably also add an "Iterate List" option.
The idea here would be to get also either a "Get Item at Index" that would have a sub-menu listing the indexes (may be a problem in the case of very very long lists) or better as Martinus suggested, a prompt that would allow us to enter an index value (integer).
This would avoid having to manually add "Get Item`nodes in between.
This concept came to me from an dynamic system modelling tool called Minsky which uses a visual programming type canvas, node and wires interface. Example
Quite often we'll have one or more nodes in any functional group of nodes where the inputs are being fed from nodes to the right and the output is going to nodes on the left. No amount of rearranging the nodes will avoid wires running right to left. Flipping the node about a vertical axis would put the input(s) on the right and output port(s) on the left.
If the redesign of Vuo results in nodes being asymmetric in the horizontal plane then flipped nodes would be more readily apparent than otherwise, and no additional visual cue would be required. If nodes frames are symmetrical, then a right to left arrow at top or bottom of node could be useful.
Here's an example of asymmetric node design, design appropriated from an old nord synth app.
It would be nice to be able to render directly to the editor background. That way the logistics of working with multiple windows will be a little less hassle when working with only one screen (less wasted screen estate). Preferrably with a node transparency option. It would also make (video) tutorials a bit easier as the result is displayed directly if screencasting or recording.
An observation ... when creating compositions I find clear layout is crucial. I find myself clumping functional units together, eg: IO section, display section and so on. Then occasionally one want to connect one part with a distant other part which often involves connections passing under nodes and immediately seems to make things messy, especially when the source or destination cannot be seen on the screen at once. This confusion also arises from links connections from the right to the left in a composition, eg: those pesky window request frame connections.
What I think would be "nice" would be a node that acts as a "sink" for data+events and another node that acts as a "source". These would be associated together by an id, or better a name. They could of course be colour coded ... seems to me this could be used to add clarity to larger compositions.