I guess to have info in the Node Library about your node it needs to be a fully compiled Vuo node. Would be good if sub-compositions could have explanatory text and links to example compositions. This would especially benefit the sharing of sub-comps in the Vuo community. Sometimes it's important to list gotcha's and limitations of a sub composition's functionality and the Node Library documentation seems like the obvious place to do it.
This would require that sub-comp contain a text field that could use MarkDown for the node documentation and links.
graphic designers have been using "package media & fonts for output" type of commands in DTP software forever.
it would be neat to be able to gather the images I used in a composition to upload to the cloud. it's not hard finding the folder they are in, but they are five out of fifty images in that folder, so I have to be very careful selecting them.
If Vuo could save the composition file and then collect all linked media and anything else that makes sense like CSV files and the update links to be in a folder at same level as the Vuo file that would be very nice. I'm sure it's not a priority!
A bypass button for the nodes to route the signal directly to the output port.
This request came from some students who participated VUO AV Workshop. Sounds like a practical idea. Sometimes this can save time when we are working on complex compositions that require a lot of testing. Instead of unplugging the cables, we can disable the node.