-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: multi layered visual DSL #152
Comments
Hi @srdjan , thank you for continuing the conversation. About:
At some point we were working on a PoC where you could focus on a node -> the node increased in size and the other nodes would get smaller. And the idea was that a node representing a subgraph would show the subgraph inside the node rectangle - similar to https://youtu.be/5Ec5yRp0SgM?t=252 (here we were showing the function source). But we postponed this effort for a while.
Could you do a simple drawing of the idea? I don't quite understand. I agree that the pipecanvas library needs improvement - I don't yet have a full picture of how exactly. But I am in a better position now, that I've introduced nested graphs. |
something like this? I just meant that graph nodes are visually represented as boxes with names vs lines... I wish I had more to add... |
I plan to revisit this when I am ready to tackle the multi-layer nested graph view. So, I will leave this issue open. |
few links to some examples, for inspiration... An open source graph node engine and editor: Flowcharts editor, but it may generate some ideas: Feenk, a moldable development tool, example: also, Tiled Grace has interesting approach to visualizing graphs, by nesting them (like scratch): |
... adding luna, visual DSL is compact but expressive: |
... continuing from the twitter thread:
https://twitter.com/lorecirstea/status/1242547389275275264
Issue: current pipeline visual representation gets very unwieldy, hard to follow, as it grows.
This issue is for discussing possible solutions...
My initial suggestion would be to investigate a multilayer approach, where top level layer could offer high level data flow (or state machine?) view that gives a high level snapshot of the pipeline functionality, but then allow a drill-down to more detailed view of the nodes/subgroups.
contracts would be boxes, at the top level, not lines and would show simple directed connections vs full, per parameter view in drill down mode...
Anyway, this is just a suggestion and call for action, since once used for a while things become familiar and is not easy to see how it appears to the newcomers...
As I said in the twitter thread. above, GREAT WORK! Congrats on progress made.
The text was updated successfully, but these errors were encountered: