Hi Jaymie thanks for your reply.
sure, as example , add an image background to a compositon that renders objects , I had to try several nodes to finally discover the image to object node.
this in maxmsp land could be easly done using a jit.matrix node. what it makes it easy is intuition = working in max visual nodes is called jitter so all the nodes related to visual are called using the ji.x prefix, and having an auto prefill features help to discover nodes quickly. matrix in max are like bridges for data. Again I love vuo , vuo takes beyond what maxmsp jitter can do, and maybe do some pre-made nodes that do the core functions could make Vuo a great visual programming tool for Artist ( non programers) like maxmsp did with vizzy and Beap. best
Vuo is just great., in my opinion and experience working with vuo is a bit confusing regarding the nodes data in / data out , ( identifying data types)
this problem has been sorted by Max msp having a name convention and clear help -sample files, for example working with visuals you usually use Jit.x or jit.gl.x
for sound nodes have a ~ at the end, the cord / lines have different coloring scheme, etc. I love vuo and want to start working more often with vuo but the editor interface will benefit from a clear emveriioment and workflow.