Another piece — "select a bunch of pre-connected nodes, right-click them into a macro and all publishing and cable connections are done for you" — doesn't have a public feature request, but we're already working on it and are planning to release it in Vuo 1.3.
We're planning to do this as part of another feature request, Get Mesh / Object Vertices. You'd be able to retrieve the shader from one 3D object and apply it to another 3D object.
For the discussion Is Within Box Get Color, I think the solution that you suggested, Bodysoulspirit, would actually be more efficient. Rather than building a list of 3D objects and then extracting their colors to send as DMX, Xavierdev can build a list of colors and use that list both for creating the 3D objects and for sending as DMX.
Hey, Bodysoulspirit, just wanted to let you know that your feature request is not forgotten :) We've been snatching time here and there to research color profiles, because it's a tricky subject and we don't want to miss anything important when planning this feature.
In case you're still having problems, another thing to try is to delete Vuo's cached files. Go to Finder (e.g. click on the Desktop), then go to the Go menu and hold down the Option key, and select the Library option that appears. Go to Library > Caches > org.vuo, find the folder corresponding to the Vuo version you have (probably 1.1.1), and throw it in the trash. Or you can trash the whole org.vuo folder. It will be regenerated the next time you run Vuo Editor.
Hi bLackburst yes, good point. That was certainly one of the intentions of my window in window mock up show above.
I used to make QC layers for BonixTV/mimoLive and at a certain point you had to add all the protocol layer stuff and save the file and open it in BonixTV/mimoLIve to test it, but at least you could keep the file open in QC and keep saving it and just reload it in BTV. Much harder though not having live testing. That's part of what makes visual programming attractive after all.
If i can get a prototype working of the pan and zoom I'll do it. I attempted it back in 2011 and it was too hard for me in the end in QC at that time. I had simple panning and cursor states changing with modifier key states for pan and zoom in/out like with Adobe products and 3D apps. But when I added the zoom functionality into the prototype it got way messy and slow which defeated the purpose of showing how cool and slick it would be. Maybe I should attempt it in Vuo (or Origami Studio!) and see if performance and functionality improves? Anything involving prototyping maps with zoom that has to track object locations is hard work in QC/Origami… I've tried with several projects and I end up giving up. Nobody else has ever posted anything that has succeeded to Origami FB page either.