Closed moodymudskipper closed 2 years ago
Confusing, let's rethink all this when we find a fitting technology for interactivity.
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary.
With better edge and node data it'll be easier to extend flow to interactive diagrams etc.
We'll be able to do better than what we did with
trim
orrange
too.I believe that we need to add a branch_id to nodes and edges.
A branch_id depends only on the
if
calls that were encountered, it's actually binary code, the first branch is1
, it can split into11
and (optionally)10
at the first if call, then goes back to1
, nested if calls will create branches111
etc.It means loops don't create branches, and the upward edge is not a separate branch either.
A branch is broken by if calls into segments, these segments have incremental ids.
The blocks on this segments have incremental ids as well.
It makes it very easy to filter out branches and view something that makes sense.
From one block we can easily extract its branch and segment, se we can have a lot more control about what we see.
Potential extensions will be able to collapse sections of the diagram easily.