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.

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 :

Fetch Compositions.png

If the Vuo editor crashes, any already-running compositions continue to run. (You can quit them from the Dock, or if they don't appear in the Dock, you can quit them using Activity Monitor.)

This feature request proposes that, the next time you launch the Vuo editor, it would detect and offer to stop any compositions that are still running after a previous crash — more convenient than having to find them in Activity Monitor.