-
Notifications
You must be signed in to change notification settings - Fork 4
Dialogs
mattjSTFC edited this page May 16, 2022
·
6 revisions
A dialog is an overlay that requires the user to interact with it and designed to elicit a response from the user. Dialogs inform users about critical information, require users to make decisions, or involve multiple tasks. Dialogs are used to direct the user’s attention to a specific task, without taking them away from the context of the current screen.
- Avoid dialogs launching dialogs: Dialogs should avoid launching additional dialogs, as they add visual complexity
- Don’t include multiple steps in a dialog: Breaking a complex task into multiple steps is a great idea, but it’s also generally a sign that something is too complex to ask users to complete within the confines of a dialog. If an interaction is complex enough to require multiple steps, then it’s complex enough to warrant its own page
- Dialogs should not include more than two actions. A third or more action will increase cognitive load and may lead to confusion as to the next steps
- Content should be kept to a minimum - keep it clean and simple. Content in a dialog should also never appear partially on screen and not contain scrollable content
References
-
Architecture
-
Dev environment
-
Developing a plugin
-
Deployment
- Deploying SciGateway
- SciGateway Settings
- Deploying plugins
-
Releasing
-
Plugins
-
Continuous Integration
-
UX
-
Feedback