Be able to export subcombs as .vuonode

From keithlang his request below, be able to also export sub compositions as .vuonode files people can double-click to install.

Regular sub compositions should still be available, they have their upsides too.

If they could be protected against opening (as an option ?), that could sound as a way to Protect shared compositions and nodes [Save composition as closed composition] ?

PS : this started as a request to double-click regular .vuonodes to install them, until I realised that is already possible.

Component: 

Tags: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro

Complexity: 

●●○○ — A few weeks of work

Potential: 

●○○ — Appeals to current community

👽 Space-out nodes

Often I'm working on some nodes, and I realize I need to insert a new node into a pretty long chain of nodes. The result is a squiggly mess, and requires quite some work to bump all the other nodes along.

Wouldn't it be great if we could say 'Space out nodes' and it would horizontally space the nodes so that there are no cases where nodes need to squiggle, just because there's not enough horizontal room.

I seem to remember other requests for 'auto neaten' of nodes. This could be pretty complicated to design, so I think we could at least start on the x axis, per this Space-out idea.

Component: 

⊹Increase grid snap size option.

I'd love if the grid snapped ONLY to the grid lines. Ie, I'd like to have less snapping options in between the lines.

My reasoning is, that the blocks of interaction I'm working with are (At least) as large as the grid already. So I'd like to keep it neater by having less options as I throw around nodes 🙂

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro

Complexity: 

●○○○ — Up to a few days of work

Potential: 

●○○ — Appeals to current community

We'd implement this as an option.

A UI for storing / editing published ports (save prefs) for screensavers

Similar to A UI for storing and editing published input port values but for screensavers.
As Jaymie mentioned there, a dedicated Feature Request would be better.

QC equivalent: 

Published Ports did work back in the days as options

Component: 

Tags: 

Notes from Team Vuo

Vuo Pro: 

Yes — requires a Vuo Pro license

Complexity: 

●●○○ — A few weeks of work

Potential: 

●○○ — Appeals to current community

Load & Play FFGL plugins

Not sure if this should be a separate feature request from Lambdas/closures — ability to pass nodes into other nodes, but this seems like a first easier step towards that if I understand that request correctly.

Be able to just fetch and render saved Vuo Protocol Files.

QC had a "Render in Image" thing if I'm right.

Also, a Vuo Composition Vuo Type, so that we can scan folders for them to pickup random ones, and drag and drop them on window compositions and fetch their URL's.

Mockup :

QC equivalent: 

Render to Image

Component: 

Notes from Team Vuo

Vuo Pro: 

Yes — requires a Vuo Pro license

Complexity: 

●●○○ — A few weeks of work

Potential: 

●○○ — Appeals to current community

Pages

Subscribe to RSS - Vuo Composition Building/Editing