Skip to content
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

visual filtering #470

Open
oliver-sanders opened this issue Jul 6, 2020 · 2 comments
Open

visual filtering #470

oliver-sanders opened this issue Jul 6, 2020 · 2 comments
Labels
Milestone

Comments

@oliver-sanders
Copy link
Member

oliver-sanders commented Jul 6, 2020

awaiting sketch

A system for changing the appearance of task nodes based on properties of the task, e.g:

  • Family
  • Parameterisation
  • (Re)Flow

This "visual filtering" is intended to make it easier for users to gain an at-a-glance overview of the higher-level-structure of a flow without needing to delve into deeper inspection.

Example use cases:

  • Style components of systems differently.
  • Mark critical components of a workflow.
  • Group parameterisations.

Suggested groupings:

  • Flow number (quite critical as this information is not presently visible in the UI).
  • Family (i.e. top-level family name).
  • Task "[meta]"data (user-defined fields).

Implementation:

  • Visual filters are orthogonal:
    • You can only have one filter at a time.
    • Visual filtering local to a tab.
    • Turned off by default though can be automatically activated by events (e.g. user creates a new [re]flow).
  • Use colour as the primary means to distinguish between nodes:
    • Since task-job separation nodes are now all grey.
    • Define a colourmap which doesn't conflict too much with the job status colours (preferably duller).
    • Accessibility Allow a user-definable colourmap for colour blind users.
  • Use opacity as the secondary means to distinguish between nodes:
    • Users toggle the opacity of a group of tasks by (de)selecting them or by hovering over the options from the filter menu.
    • Accessibility This does not depend on colour at all.
@oliver-sanders oliver-sanders added this to the 1.0 milestone Jul 6, 2020
@oliver-sanders oliver-sanders mentioned this issue Jul 6, 2020
4 tasks
@oliver-sanders oliver-sanders added design question Flag this as a question for the next Cylc project meeting. labels Jul 7, 2020
@kinow kinow modified the milestones: 1.0, 2.0 Sep 10, 2021
@oliver-sanders oliver-sanders modified the milestones: 2.0.0, Pending Jun 8, 2022
@oliver-sanders oliver-sanders removed the question Flag this as a question for the next Cylc project meeting. label Jul 25, 2023
@oliver-sanders oliver-sanders modified the milestones: Pending, 2.1.0 Jul 25, 2023
@oliver-sanders
Copy link
Member Author

This has risen up the priority ladder partly as a result of planned changes to cylc remove which would see it strip flow-numbers from tasks. This needs to be communicated through the UI to make sense.

@MetRonnie
Copy link
Member

MetRonnie commented May 29, 2024

Proof of concept flow nums display added in https://github.com/MetRonnie/cylc-ui/tree/flow-nums

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants