In a similar fashion, I've taked the internal "flow graph" inside my
compiler and generated a flat/subgraph view of use case 5.30 (which
is faily complex).
In my graph, viewports/groups/etc. have their inputs and outputs
represented by vertices in the graph as they can be viewed as
special kinds of components that handle meets/joins in the graph
as well as other semantics.
Also, I've left out all statically determined inputs as components
can get those at any time. What is left is the flow of the data
through the pipeline.
--
--Alex Milowski
"The excellence of grammar as a guide is proportional to the paucity
of the inflexions, i.e. to the degree of analysis effected by the
language considered."
Bertrand Russell in a footnote of Principles of Mathematics
