Should audio.io.Node be used as a "controller"? It could create Views and Models...
Regarding communication between Nodes, Views, and Models:
At the moment, Views create their Models. Maybe a Node should create the Model then comms from View to Model could go thru the Node, and comms from Model to Node and vice versa are built in to the Node...
Marking as closed. A Controller class has been created that creates a specific View, Model and audio Node for itself. All communication goes thru the controller.
Should audio.io.Node be used as a "controller"? It could create Views and Models...
Regarding communication between Nodes, Views, and Models: At the moment, Views create their Models. Maybe a Node should create the Model then comms from View to Model could go thru the Node, and comms from Model to Node and vice versa are built in to the Node...