On Wed, Jul 29, 2009 at 10:19 AM, Andrea Valle
<valle@xxxxxxxxxxx> wrote:
What sort of syntax do you have in mind.
I'm prototyping the thing described in attachment. (Actually the examples work here, but I'm in the middle of the operations...).
Interesting, but also has the risk of being Yet Another Abstraction that may not play nicely with others. Don't get me wrong - it's a very cool idea (!), nice bridge for people who are used to Max scripting, but I think a main-library standard solution should be lighter weight and more in line with current object-style usage.
What if we adapted the node ordering logic from MixerChannel to nodes? You would do:
sourceNode.sendsSignalTo(receiverNode);
And information is then stored in the node object that the reordering code would use to make sure sourceNode is always earlier. Break the connection with:
sourceNode.stopsSendingTo(receiverNode);
hjh