gcylc - keep view options client-side about cylc-ui HOT 6 CLOSED

Notes from discussion to move to cylc-web:

• (Matt) Browser cookies? Or user session settings on server side? Should probably move to cylc/cylc-web.
• (Hilary) Agreed. Not sure how to do it yet, but we don't want one user's family-collapse choices to affect other users viewing the same suite (as happens now)

from cylc-ui.

Currently lib/cylc/config.py computes the final pygraphviz graph structure that is plotted by the gcylc graph view (and the suite graph tool). This includes replacing family members with nodes representing collapsed families, so config.py (in the main program) keeps track of which family nodes are collapsed. This dates back to early cylc graphing days, prior to the gcylc graph view, when family collapsing was statically determined by the suite visualization config alone.

Another side effect of the current situation is that gcylc client graph views put extra load on the server, to compute graph updates.

The server (via config.py) should only compute (once) the static abstract graph structure determined by the suite definition, and all computation of the actual pygraphviz graph for the current task pool (gcylc) or a particular cycle time range (the graph tool) should be punted to the client programs.

from cylc-ui.

When we do this, we should also allow families to be grouped/ungrouped for a single cycle time, rather than for all cycle times present.

from cylc-ui.

I'm going to delay this until the communication refactor, if that's OK.

from cylc-ui.

That's OK.

from cylc-ui.

Superseded by #335

from cylc-ui.