Another pseudo-subnetwork idea. User can select a connected subset of a network, and define a custom module that can be saved and reused. Similar to snippets or saved fragments, but with an encapsulating GUI that makes it look like a single module in the larger network. I have some of the GUI infrastructure for this already; if I used a wizard/builder for choosing what the input/output ports were, I could simplify the subnet GUI and make it read only, which would make the UI code much less complicated. I could also test this on the network layer separately. They could be saved as part of a network too, to ease sharing as part of a toolkit.
The result would be a higher-level view of networks, to encourage batch-processing and more general testability as suggested by @jab0707 and @bzenger.
Another pseudo-subnetwork idea. User can select a connected subset of a network, and define a custom module that can be saved and reused. Similar to snippets or saved fragments, but with an encapsulating GUI that makes it look like a single module in the larger network. I have some of the GUI infrastructure for this already; if I used a wizard/builder for choosing what the input/output ports were, I could simplify the subnet GUI and make it read only, which would make the UI code much less complicated. I could also test this on the network layer separately. They could be saved as part of a network too, to ease sharing as part of a toolkit.
The result would be a higher-level view of networks, to encourage batch-processing and more general testability as suggested by @jab0707 and @bzenger.