Closed jodigiordano closed 2 months ago
By multiple flows, what exactly do you mean?
@Stan-Stani: If you look at the JSON of this system (view > json editor), you will see:
{
"flows": [
{
"title": "flow 1",
"steps": [
{
"keyframe": 0,
"from": "foo",
"to": "bar"
}
]
},
{
"title": "flow 2",
"steps": [
{
"keyframe": 0,
"from": "bar",
"to": "foo"
}
]
}
]
}
So it is currently possible to define multiple flows for the same system but there is nothing in the UI to CRUD those multiple flows. Right now, there is a lot of hardcoded code that only works for one flow.
The idea of supporting multiple flows is to create a system once, and then show multiple use cases of that system. For example, here's a use case and here's another use case. Those are 2 completely independent graphs however. It would have been nice that I give you 2 links that looks like:
https://gg-charts.com#file=<X>&flow=0
https://gg-charts.com#file=<X>&flow=1
I'm pivoting this project to a general diagramming tool so there is no need for this feature anymore. Sorry!
@jodigiordano Would you mind explaining your decision to remove the animation of the flows? Just trying to figure out why that feature was removed. General diagramming tools don't need animations? :) 🧐
Currently, the specification of a system (i.e. YAML) supports multiple flows but the editor / presentation only support one flow.
The current workaround is to duplicate a system to create another flow.
Instead, it would be useful to CRUD flows in a same system to present multiple use cases.