Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
DSDP/MTJ/Modify Component
Use-Case Specification: Modify UI component
1. BRIEF DESCRIPTION
The user can alter the properties of selected components in the UI designer. Properties change the outlook and behaviour of components. If components have similar properties, more than one component can be changed and common properties for them all can be changed.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user decides to modify a UI component.
- B2. The user selects the component he wants to modify.
- B3. The user opens the property list for the component.
- a) The system opens the list showing the properties and values that can be changed for that particular selected component.
- B4. The user selects the property to alter.
- a) The property editor opens, allowing user to alter the value of a property. Different properties can have custom property editors.
- B5. The user alters the property value and accepts the change.
- a) The system updates the code according to the changes performed.
- b) The system updates the property value in the UI and updates the UI according to the changes performed.
2.2 Alternative flows
- Alternative flow 1: In-place editing
- A1. The user can activate in-place editing for certain properties (e.g. text) when a single component is selected. When in-place editing is activated, the editor for a property opens in the UI designer and the user can edit the property directly in the UI editor.
- Alternative flow 2: The user edits the component by editing the code
- A2. The user edits the code to change the component. The UI designer notices that the code has changed and updates the component’s outlook and the property list accordingly.
- Alternative flow 3: Multi selection
- A3. The user can select multiple UI components and modify their common properties. When multiple UI components are selected, only the properties that are common for those containers are selectable and editable. After editing the property, the new property value is updated for all of the selected UI components.
- Alternative flow 4: The user gives an invalid new value for the property
- A5. If the user gives an invalid new value for the property being altered, the system will warn the user about the invalid value and reverts the property back to its original value.
- Alternative flow 5: Eclipse refactoring
- A6. If the user performs Eclipse refactoring while the UI designer is open, the system will inform the user that refactoring has been performed and components in the designers have been updated accordingly.
3. SUBFLOWS
4. KEY SCENARIOS
5. PRECONDITIONS
5.1 Precondition 1: The UI designer is running and has one or more components
Component properties can only be altered when the UI designer is running.
6. POSTCONDITIONS
6.1 Postcondition 1: The property of the selected component is changed
The Property value visible in the property list is updated for the selected components and the code is changed. If the property affects a component UI, then the component will be redrawn with new property values.
6.2 Undo is available
The undo feature will be available to undo the latest change.
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases