One GUI using technology for web applications
- gcylc: large memory footprint in graph mode - possible leak?
- Close as superseded by One GUI using technology for web applications.
- (Matt) Close.
- gcylc - better command output display?
- Would have to be re-scoped for cylc/cylc-web or closed.
- (Matt) Move to cylc/cylc-web - how can this be done better in the web UI?
- gscan misc view improvements
- Close as superseded by One GUI using technology for web applications.
- (Matt) Close.
- Document how to change GUI font-size
- Close as superseded by One GUI using technology for web applications.
- (Matt) Close. Can use themems/CSS in the future? Accessibility issue?
- dynamic 'best fit' in GCylc's graph view
- Close as superseded by One GUI using technology for web applications.
- (Matt) Are we still going to have this issue in the web UI? Probably depends on the graphing framework we choose.
- cylc gui tree view progress bar
- Close as superseded by One GUI using technology for web applications.
- (Matt) Close.
- GUI: unused view memory release?
- Close as superseded by One GUI using technology for web applications.
- (Matt) Close.
- cylc gui: keyboard interrupt handling broken
- Close as superseded by One GUI using technology for web applications.
- (Matt) Close.
- gscan: unstable folding
- Close as superseded by One GUI using technology for web applications.
- (Matt) Close.
- cylc graph (readability): node labels always white
- Close as superseded by One GUI using technology for web applications. (Unless fixed for cylc-7.8.x)
- (Matt) Accessibility for 7.8.x.
- cylc graphing: optional branching
- We should move to cylc/cylc-web repository if we still want this feature.
- (Matt) Move to cylc/cylc-web.
- multi-level family expand/collapse in the dot view
- Move to cylc/cylc-web repository I think.
- (Matt) Move to cylc/cylc-web.
- Show external trigger values in the GUI.
- Move to cylc/cylc-web repository I think.
- (Matt) Move to cylc/cylc-web.
- Remove redundant graph edges.
- As we are moving the graphvix logic the cylc/cylc-web, I think this must be moved to cylc/cylc-web repository.
- (Matt) Move to cylc/cylc-web.
- gcylc - surprising behaviour with families and multiple inheritance
- Move to cylc/cylc-web repository I think.
- (Matt) This is also a general problem due to families being used for both runtime settings and graphing.
- cylc graph - search for task?
- Move to cylc/cylc-web repository I think.
- (Matt) Move to cylc/cylc-web.
- New GUI: scalable navigable matrix (quilt) view
- Move to cylc/cylc-web repository I think.
- (Matt) Move to cylc/cylc-web.
- Finer-grained authentication and authorization
- I wonder if we need a sibling issue in cylc/cylc-web? There will be some discussion about authX in cylc/cylc (change granularity, add new roles/privileges, etc) and also in cylc/cylc-web (use tokens, refresh time, technologies used, which JS library to use, etc) I believe.
- (Matt) Yes.
- Future Cylc Authorisation / GUI Architecture
- I think this and the previous issue need to be reviewed, and either both updated, or one closed, so we document everything in one issue only, which will be included in CHANGES.md later.
- (Matt) Combine this with the previous issue and split it up again for cylc/cylc and cylc/cylc-web?
- cylc run --set=NAME=VALUE inputs persistence and gui issues
- If we want this feature of storing the name=value in the GUI, then we must move it to the cylc/cylc-web repository.
- (Matt) Yes. Values are stored in the runtime SQLite file. We need to be able to enable read/write from the web UI.
- gscan for all registered suites (or a subset of them)
- Move to cylc/cylc-web repository I think.
- (Matt) Yes.
- cylc graph, cylc gui graph view: nice way to specify node images
- We should move to cylc/cylc-web repository if we still want this feature.
- (Matt) Yes.
- (re)allow independent filtering of views
- Move to cylc/cylc-web repository I think.
- (Matt) Yes.
- suite report utility
- I think this is possible in the Web GUI, and would be quite useful. We could allow users to print, export as PDF, CSV, etc.
- (Matt) There are 2 parts. We need to collect more relevant data, and then we need to serve the data on the web UI.
- Colour coded task names in LED view
- If we will have a LED view in the Web GUI, then this issue must be moved to the cylc/cylc-web repository.
- (Matt) Yes.
- internationalization of user visible strings
- Q: We will have i18n in the Web GUI. Do we still need it for the command line?
- (Matt) Yes for help strings (and interactive prompts?)
- gcylc - keep view options client-side
- Not sure how that plays with the Web GUI?
- (Matt) Browser cookies? Or user session settings on server side? Should probably move to cylc/cylc-web.