I only play with Vuo sporadically ATM and I frequently forget the relationship between some of the more complicated datatypes like 2D Objects, 3D Objects, Meshes, Scenes, Layers, Images, Shaders etc.
Often when I want to expand a composition with a specific enhancement I’m scratching my head as to what direction I should be working in, am I looking to add a 3D object shader to a mesh that currently has an image shader and set of points as inputs, or should I be piping 3D Objects into a layer node≤ or what have you.
I’d like to see what these advanced but very important data types actually look like in code terms, how is a 3D Object type defined? Is it a super class which the {line, cube, sphere, torus,…} set of objects belong to? How is a Scene defined, is it a class containing 3D objects and shaders assigned to each 3D object? How is a mesh defined, is it simply a list of 3D Points or also 3D objects, or is it a 3D object itself, does it take or require at least a simple shader definition?
To graphics programmers and 3D modellers this is probably more readily apparent, but seeing as Vuo takes the approach that it’s also a programming tool for those without much coding experience I really feel there needs to be some structured overview and maps to these components. (That’s how I like to think about it all anyhow, I want the map even if I don’t understand the complexity of many of the things shown on the map beyond their name and basic purpose).
We could start it as doc in the cloud using Pages or Keynote (seeing as we’re all on Mac) and then Kosada could correct it and integrate as part of the documentation. Put in the Appendix of regular docs maybe. Some diagrams would help, we’re visual types.
Other data types worth considering are lists, and that sub-set of nodes that accepts a list input, but it’s more the 3D imaging/scene construction that I want immediate clarity on using some maps and explainers of each type of node/data class.
I have scanned the manual, but the manual tends to a more narrative approach, I’m looking for something more like a listing of the 3D related objects and their relationships to each other. I guess the VUO API documentation is a place to start, but a less technically dense, more user friendly approach is what I’m advocating for. Mostly for beginners but for advanced users too if they forget something or are looking for more depth around certain functionality.
The document would assumes basic knowledge of Vuo operations like connecting nodes, firing of events, iterating loops… but would help in overall composition design when you have no idea how to approach a very specific end goal. IN some ways a pattern book.
If users concur I’m happy to start it, but not knowing too much I can’t really write it on my own.