A question and suggestion.

How do people handle sub-composition when it comes to distributing compositions. For example, I might have a number of subcompositions I've created and use regularly, they are located in my node library. When it comes time to pass the composition I'm working on to others it is easy to miss a required subcomposition ... or just time consuming to find them and test.

Suggestion, a new save or export choice which has an "include sub compositions" option.

Comments

As written here Option to

Bodysoulspirit's picture
Submitted by

As written here Option to edit subcomposition without affecting other instances — Group nodes just for organization, not for adding to Node Library, there will likely be 3 kind of sub compositions, global (the ones we have now), local, the same as now, added to the library but where the changes made will only affect this sub-composition and somehow a real local sub-composition, actually simply a group of nodes, more like the QC sub-macro.

While the last one, real local group of nodes will allow seamless exports for sharing (as Jaymie mentionned here : Ability to create composition-local subcompositions, for the others I don't know either.
I know there is this feature request about being able to use sub-compositions not located only in the user modules : allow modules to load from user and system folders from inside sub-folders, so I guess you could somehow link to them with the url like an image and bundle them in a folder with the composition using paths.

But I have always wondered if in the end compositions could not be some kind of bundles, like apps actually, with a part of them having the code, but that we could also bundle sub-compositions (password protected or not ((see Feature Request about protected compositions for sale purposes)), modules, images, movies, fonts etc).
These would be absolute shareable compositions.