Use Cases and Scenarios for Floating Windows
Author: Jindrich Dinga
Date: July 2006
Version: Final
Content:
- Use Cases and Scenarios
- Floating Window
- Floating Editor
- UI Specification
1. Use Cases and Scenarios
Because almost all requirements are related to multi-monitor support, we suppose that users have at least two monitors in the following use cases. Same steps are also valid for users with one monitor, however they are not the "primary" target audience for us.
1.1. Floating Window
This section covers two similar use cases with the same usage scenario:
UC-1: The user is creating e.g. a GUI application and wants to undock Palette and move it closer to the object s/he is currently designing.
UC-2: The user wants to increase the workspace as much as possible so s/he drags windows, s/he often interacts with, on the second monitor
Scenario:
- user drags the window outside the IDE and places it on the second monitor
or
- user selects the action from Window menu/contextual menu invoked on title bar of the window
- the window becomes floatable
- user drags the window on the second monitor
1.2. Floating Editor
This section cavers the primary use case we support.
UC-1: The user wants to copy lots of content from a file to a new file. S/he wants to see both files at the same time.
Scenario:
- user drags the editor tab outside the IDE and places it on the second monitor
or
- user selects the action from Window menu/contextual menu invoked on editor tab
- the editor tab becomes floatable
- user drags the tab on the second monitor
2. UI Specification
For UI specification click here.
