Make it easier to share (and archive) compositions that use external file resources.
Would love more info on this !
How would the team envisions this ?
Could be a File > Export > Composition Archive menu item. It would take the composition, all media it uses, all plugins it uses, and combine them into a ZIP file. You could then easily upload that ZIP to the Composition Gallery. Another person could download the ZIP and open it in Vuo Editor and run it.
Related: Ability to create composition-local subcompositions. Actually that would probably be a prerequisite, since otherwise you couldn’t easily load all of the plugins from the ZIP file.
Wouldn’t it be technically possible that a vuo file would instead be a small little bundle, with the ability to contain files, like an app can, and have the actual .vuo code file be bundled in it too?
I guess the team probably thought about this so there may be some cons to this or maybe it wouldn’t be possible, and if it’s possible, it would probably require way deeper changes and change the complexity to more dots.
This would probably be the easiest way to share compositions no ?
Yes, that would be possible. You already pointed out the pros, so I’ll just mention the cons:
- You can’t upload bundles directly to websites. You have to zip them.
- To see the contents of a bundle, you have to know to use the context menu and pick Show Package Contents.
@jstrecker good points.
Yeah I was just trying to think long-term.
Mainly we need to pack :
a) Files (images, fonts, xml’s etc).
b) Sub-compositions / local compositions.
And this for :
- Compositions (normal, filter & generator).
- Apps (it’s already bundling it).
- Screensavers (hope we will be able to bundle stuff like application bundles can).
- For the upcoming plugin export features (FFGL etc) I don’t know how those formats / apps manage side files & bundling.
And we use these :
A) With Vuo, as .vuo files.
B) As stand-alones (Exported apps, screensavers).
C For host applications (Coge, Resolme, etc).
I was just trying to think about what would be the most hassle-free method when it comes to sharing.
For B) as apps it’s obviously not a problem since they bundle.
For A) as .vuo files it depends, we can
- for a (files) put them in a folder next to the composition, and maybe yes an export function into a .zip that copies all the used files automatically would be a +. Here is where my pros would shine and the cons you mention too.
- for b (sub-compositions) I guess the combo "Ability to create composition-local subcompositions + Load nodes from composition path and other custom folders will allow us to solve that problem like for a (files) and just put them alongside the vuo file.
And this will be even easier with Option to edit subcomposition without affecting other instances — Group nodes just for organization, not for adding to Node Library in case these sub-compositions are stored as code inside the .vuo file itself, instead as come-along separate sub-compositions for the local sub-compositions (as I mentioned here but edited my comment when I realized I posted on the wrong feature request, in other words I hope these will be part of the main vuo file code like quartz composers patches if I’m right).
For C) as plugins for other hosting applications, again I think it depends how those apps manage side files. Clearly as I imagine the vuo files have to be moved to some specific folders, it usually requires changing paths etc, so I guess that’s where this bundle into would benefit the most if possible. EDIT : I just saw the first FFGL export from the 1.3 beta exported by the team, clearly those seem to accept side files. So it seems the only apps that would benefit vuo file as bundles would be apps that directly host .vuo files, such as Coge.
Anyway, just leaving this idea here, wanted to ask and share, maybe this will popup later again at some point. Thank you for the answer.