Ticket #157 (new enhancement)
More flexible structure of studio
|Reported by:||https://www.google.com/accounts/o8/id?id=aitoawmazmxfhpyaklskeqvmnmzj08_mnyn1lpy||Owned by:||-|
Currently we have model where is one virtual graph (studio) includes all other graphs (rooms), without ability to connect graphs directly (only through studio). But let look, how it is implemented from raw jack view point.
Each port between studio and room is implemented by jmcore as pair of input and output. One port is added to studio, another - to room. What if we want to connect two rooms directly (as much as two applications in these rooms)? In this case we need additional ports for both rooms to route necessary wires. We have to do this connections set for each connection: two connections between apps and room internal interface and one - between rooms, in studio.
Another way is to connect rooms directly each to other. In this case we have only two connections, since one jmcore in/out ports pair routes directly from one to another room. In this case "Room" term loses its meaning; the better matching name is "Space". We have set of spaces, which are not nested each to other, and may be connected to any web. Yes, spaces could be connected / disconnected manually, and this work could be done via special graph - "subspace" (hehe). There could be default graph to show external application. This graph could be set for each application by rules.
Subspace connections could be done just by special dragging of one space to another.