-
Notifications
You must be signed in to change notification settings - Fork 29
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
Rewrite editor navigation model #1870
base: main
Are you sure you want to change the base?
Conversation
b02e6ba
to
8a1b9af
Compare
- Add workflow explorer treeview - Allow navigating to any level without opening previous levels - Allow visualizers to run uncoupled from the workflow view - Highlight build errors in explorer treeview
Early feedback from the preview is that allowing opening of independent tabs and windows should be allowed in the editor control to allow watching different parts of the workflow. We could take this opportunity to generalize tabs and floating windows into a single dock panel. The main concern is going to be how to handle multiple windows pointing to the same path, and what to do when deleting group nodes causes invalidation of multiple open tabs. For the first issue we could consider enforcing that windows are singleton w.r.t. a unique path, which would obviate having to synchronize multiple view states of the same workflow. For the second issue we could probably store it in the undo/redo stack as we did in the previous navigation model by closing as a command and scheduling reopening of tab/window pointing to the deleted path with same settings in the undo command. Another option is to restrict navigation to only one window and have secondary windows used only as read-only or watch views. |
This required also devising a reasonable strategy to represent that a workflow is disabled. Currently this is done by graying out all nodes inside a disabled nested workflow.
Fixes #1823
Fixes #1993
Fixes #2000
Fixes #2001
Fixes #2004