You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The workflow editor should be divided into two modes: developer and user mode. Developer mode can be the current workflow editor while the user mode should be added - limiting the options the user can do. Here we assume that the user only manipulates input data and results, and runs the workflow, and is not able to edit the workflow, kind of "easy-to-use-mode".
(Related, database editor should also be similarly divided into input and result modes, where the current setup acts as input mode, and result mode should be developed. There's an issue of the functionality of the result db mode: #2590. The impact on the workflow editor side is that in developer mode the workflow builder names in which mode each database should be opened in by default.)
A simple mockup on what the workflow editor in user mode could look like:
Select execution: Define possible executions on developer mode side.
Select scenarios: Filter databases based on 'Select execution'. In addition to scenarios that are sent to the next tool, there is an option to execute the scenario in all following tools.
Only other toolbar items are 'Execute', 'Stop', 'Open console and event log' and 'Open developer view'
Properties widget is completely hidden, there's only a dropdown list of functions the user can perform on the item, usually just opening the file or opening the directory where the file is, and in case of databases also purging and linking to a new database.
Console and event log should open on clicking any item
Nice to have features (low priority):
Zoom to / highlight execution selection in design view (in case of large workflows)
Choose which items are shown in user mode and which are not
To be implemented later, when Toolbox has all the prerequisites:
Ability to update the tools and migrate the data to a new version (that has been approved/registered by a workflow developer)
In terms of user experience development, I have labeled this 'high priority'.
The text was updated successfully, but these errors were encountered:
- This is the first version with still a lot of broken and missing features. There's a new ToolboxUIBase
class, which contains a QStackedWidget with two QMainWindow pages. The Main window is now
either in 'expert mode', which is the old ToolboxUI main window, or in 'user mode', which is a brand
new ToolboxUILite main window.
- Fixed the resizing problem in Properties dock widget
Re #2794
The workflow editor should be divided into two modes: developer and user mode. Developer mode can be the current workflow editor while the user mode should be added - limiting the options the user can do. Here we assume that the user only manipulates input data and results, and runs the workflow, and is not able to edit the workflow, kind of "easy-to-use-mode".
(Related, database editor should also be similarly divided into input and result modes, where the current setup acts as input mode, and result mode should be developed. There's an issue of the functionality of the result db mode: #2590. The impact on the workflow editor side is that in developer mode the workflow builder names in which mode each database should be opened in by default.)
A simple mockup on what the workflow editor in user mode could look like:
Nice to have features (low priority):
To be implemented later, when Toolbox has all the prerequisites:
In terms of user experience development, I have labeled this 'high priority'.
The text was updated successfully, but these errors were encountered: