I'd like to be able to make submodules with generic published ports.
This seems like the biggest ontological hurdle separating submodules from the rest of the node library.
It would be handy for building control flow components like "select".
Feature status
- Submitted to vuo.org
- Reviewed by Team Vuo
- Open for community voting
- Chosen to be implemented
- Released
When we (Team Vuo) plan each release, we try to implement as many of the community's top-voted feature requests as we have time for.
If anyone would like to help this happen sooner, we're also accepting open source contributions and commissioned work.
Read more about how Vuo feature requests work.
Votes
80 votes so far!
Who voted?
Comments
Opened for voting.
Opened for voting.
Please explain @ajm how you
Please explain ajm how you would make a "select" component if generics were able to be published. I'm only half getting it ATM.
@Alastair, if you were to
Alastair, if you were to build a subcomposition that swaps two values, you'd have to pick a data type for the values when building the subcomposition (or else you couldn't publish the ports). Thus if you built one subcomposition that swapped text, you'd have to build a different one to swap images, and a different one to swap integers, etc. If generic ports could be published, then you wouldn't have to decide the data type at the time of building the subcomposition. The same subcomposition could be used for different data types.
Swap subcomposition.png
Swap node.png
Yes, much needed feature!
Yes, much needed feature!
With the benefit of a little
With the benefit of a little Vuo experience this is a must have feature! (Hope it isn't a big refactor of Vuo to allow for this functionality, there's so many must have features in the pipeline of requests).