dir people interested in our nextbigthing that is VL,
we've taken a bit of rest after node15 and are getting back into our business of creating serious visual programming experiences...
Feedback regarding VL so far has been cautiously positive and some of you already encountered the most pressing features that are still missing. On our road ahead we want to ask you to help us identify the best order in which we implement things. So of our long list of features that we're definitely going to implement, we've extracted 5 for you to vote on.
Regarding the selection: Those features are only the top five results of our internal voting. Also they only include features we thought we can clearly communicate. Of course there are many other issues we'll address independently anyway.
Think shortterm: Which of the following features could your patching most benefit from?
Voting ends on June 14th.
Why Flattr? This excludes a large number of people who can vote?! Well, first, anyone can easily sign up to Flattr here, and on the other hand it specifically invites those who probably take this a bit more seriously. So this is an experiment. Looking at the list of vvvv flattr users it seems that we have a potential of 27 votess in total at the moment. Lets see how this goes..
Still not sure about that flattr thing? Read the rationale again: Flattr on vvvv.org.
Very much looking forward to your votes,
Love the flattr idea for votes.
this made me sign up to flattr, thank you!
one person can now decide between type browser and dynamic pin counts... ;)
where can i flattr the API? :P
That was quick
i was one of the supporter of the dynamic-pin-count--thingie..
i really like the solution for *+-... sweet
so, i just wanted to tell you, that this would be perfect for cons,concat ...imo
Well it should be there for Concat. For now it gets applied to all nodes following the signature (Input, Input 2) -> (Output) and type of Output is a subtype of type of Input. If you build your operations the same way the dynamic pin count will be applied to those nodes too. The system internally simply replicates the node in question and connects the in- and outputs.
Cons doesn't follow that signature and therefor the feature can't get applied as it is right now.
Also note that the Enabled pin works in a similiar fashion, should a node follow the signature (Input, ...) -> (Output) the enabled pin will be added. Internally the node will be wrapped in an if region.
true concat works already, cool,
btw the enable pin has always the first input as default, thats a bit strange but maybe just a point of getting used to it.
it would be cool to use the enable-pin as a sample+hold-button? like: when disabled the output will not change, now the output still changes when disabled..
@hrovac: think with properties and objects, if you set a property of an object it will stay that way until you set it again so you don't need S+h
anonymous user login