For a network developer, there is no clue to how operators are cooking, excepted at looking each node individually by middle-mouse clicking on them.
And even then, there is only the number of times that the operators cooked, and not the sequential information of it (its history).
So, the lack of information regarding the sequence of operators cooking makes it difficult to construct and to debug networks.
It’s why I would suggest several important things (to me) in this domain:
1)-the ability to reload an entire network inside the editor and to monitor its cooking processes, by sequences.
2)-the ability to isolate/differentiate what belongs to Touch Designer Editor and what belongs to the Network User Project
3)-monitoring the network operators in ms (and not in frames)
4)-Choice for the user to monitor an entire network or subsets of a network (selection by groups for examples)
A strong editor monitor/debugger solution is necessary I think, for building networks without having to guess how Touch Designer deals internally with its operations, behind its abstraction layers.
Thanks for having listened.