Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
DSDP/MTJ/Remove Container
Use-Case Specification: Remove Container
1. BRIEF DESCRIPTION
The user can remove a container from the UI design.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user selects the container he wants to remove.
- B2. The user removes the container from the UI designer.
- a) The system updates the code by removing the generated code for the container. The removed code contains the code for child elements and the code for events. Imports are not removed.
- b) The system removes the container and all of its components from the UI designer.
- c) The UI designer UI is redrawn to match the changes.
2.2 Alternative flows
- The user removes the container from the code
- A1. If the user removes the container in the code editor, the system notices the code has been changed and re-parses the code for design. This effectively removes the container from the UI designer.
- The code file cannot be deleted
- A2. If the code file cannot be removed, the user is informed of this and container deletion is cancelled. This can happen, e.g. when some other program has locked the code file.
3. SUBFLOWS
4. KEY SCENARIOS
5. PRECONDITIONS
5.1 The UI designer is open for a main container
The UI designer is opened for the base container that includes a container the user wants to remove. The base container has one or more sub-containers.
6. POSTCONDITIONS
6.1 The sub-container is removed from the parent container
The removed container and all of its components will no longer be visible in the UI designer and all associated code is removed.
6.2 The undo feature is available
The undo feature allows the user to undo the removal of the container.
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases