Currently use QC to make custom layers for Bonix TV - a vision mixing kind of application for OS X with a kind of QC stack of layers, each layer being a composition with published ports and some protocols for data types. Also generate sports graphics and twitter feeds and so on for video score boards at large sporting venues.
Spent a few years learning Quartz Composer as my way back into coding from a decade away doing design related work. Film, graphics, studied Architecture for a few years and got involved in publishing then film. Now moving into front side web development. Hope to get into app dev with Vuo and rapid app prototyping.
I think Vuo would benefit tremendously for ease of use by new users in making these types explicit and even changing the wire thickness/dashes or port shapes to make this more explicit.
Images are bit format. Scenes, shape objects and layers have their unique structural definitions. It’s not clear to the new user how to proceed a lot of the time given the large number of processing nodes that are specific to one or another data type. It’s a catch 22, until you learn about all of them your end up chasing your tail a lot in Vuo in my experience.
Thanks Magneson. I wish this node suggestion came up when I typed in "layer dimensions", "image dimensions", "Text Dimensions", "Text Size", and a dozen other things into the Node Library (which actually is usually pretty good at matching needs, even with QC patch names with a similar function).
This has to get more tags in the Node Library, I will FR It,
I think the main issue I have in self-tuition with Vuo (ironic given the aspiration that it were to a be code tuition tool in eduction) is that there's a lot more types than in QC and other node programming environments. It's very hard to see beneath the hood sometimes, where as QC was pretty literal in what it passed around, mostly just primitive types and structures. It's good that Vuo has more sophisticate type data being passed around, it can be more powerful, and I envisaged that going a lot further in Vuo Alpha 0.1 days but I think there needs to be some kind of inspection tool that lifts the hood on what is being passed around. Also wires should be colour or dot/dash coded to not special instances of datatypes. Dunno but it's a buffer to learn this for me. I tend to think in first principles and getting the maths sorted first and seems like Vuo has all these tricks that offer less control but more shortcuts, if you know them and they fit what you are looking to do.