-
Notifications
You must be signed in to change notification settings - Fork 27
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
Custom Visualisation #263
Comments
Apart from my never-merged experiment for the old GUI, the We still need both:
For case 2. we should allow small badges of customizable colour, on the task icons? (Any more than that and we risk obscuring the meaning of the task icons). |
This is something which kinda bugged me about Cylc7, you could customise the hell out of the static graph appearance but when you actually ran the suite it looked completely different. I would prefer to only support minimal customisation for both but develop more advanced grouping and representation systems for the future built around sub-workflows, parametrisations and logical task groupings without the need for manual configuration. |
Huh, I see the two use cases as very different:
I do agree about advanced grouping and sub-workflows etc., but I think that's orthogonal to the kind of styling I'm talking about. The kind of thing that is nice for presentations and impressing managers, but useless for a control UI: |
I kinda feel that this is just as important for monitoring / control, the aborted PR cylc/cylc-flow#1932 shows the desire for uniformity between the two. Rainbow suites are admit-ably kinda cool, but I don't think they do the best job of conveying structure. Using your above example, collapsing parameterisations would make it much clearer. |
I totally agree that we should have the kinds of grouping you've illustrated above. (Something else to think about for the graph view @MartinRyan !) There may still be a good case for arbitrarily customizable styling of static graphs though - e.g. to highlight sections of a workflow during presentations, or just to make your workflows look as impressive and sophisticated as possible. However, we can worry about that later. |
Might be useful for graph collapse?: https://github.com/iVis-at-Bilkent/cytoscape.js-expand-collapse (From #74 (comment)) |
Supersedes #58
See the Cylc Flow counterpart - cylc/cylc-flow#3379
Open up the ability for minimal customisation of the appearance of tasks / families.
The main use case for this will be visually distinguishing between different groups of tasks (e.g. ones belonging to a particular model or system).
Now that task icons are not colour dependent we are free to use colour for this, see the design issue (#87) for more info.
This is roughly analogous to the old
[visualisation]
section in Cylc 7 which allowed users to specify custom Graphviz attributes.The text was updated successfully, but these errors were encountered: