refs 2726

refs 2726

refs 2726

refs 2726

Ensure that IDs have been assigned to all new model elements before they are hooked to the project / resource
- Rationale
  - Model elements for which no ID has been assigned, have id 0 (which is the default value). 
  - When the new element is hooked to the resource, ResourceUtils.KernelResourceFactory.KernelXMIResource.getId() is called, which internally calls setId() to synchronize the XMI ID with the AF3 ID. In case the ID is still 0, this implicit call will corrupt the ID -> model object map (by override the mapping for key 0).
- Changes
  - ElementCompositorService: Assign IDs *before* hooking new element to the container (but of course using the container to determine the next free ID)
  - ModelElementCompositorBase: Assign IDs to newly instantiated annotations

refs 2726

refs 2726

refs 2726

refs 2726

refs 2726

refs 2726

refs 2726

refs 2726

refs 2712

- This is expected to create the right bundle URIs when the code is executed from a deployed bundle (in an RCP)

refs 2361

- Add a mechanism to create input dialogs: The action descriptor passes a map-type object that defines the expected parameters.
- Refine the container classes.
- Add an annotation action that allows to create random valued entries for a selected annotation build around an average value and the given bounds.
refs 2361

- Move the annotation and annotationEntry fields from the ColumnHandle to the AnnotationInstSpec class.
- Add a container class to the IAnnotationValueProvider that allows to specify the menu entry string and the set of elements to apply the specified action to.
- Modify the IAnnotationValueProvider and DefaultAnnotationContextActions interfaces to use the new container class.
- Adjust the GenericAnnotationView to create runnables based on the information found in the new container class.
- Simplify the "Propagate to all" annotation action.
refs 2361

refs 2709

refs 2709

refs 2703

refs 2708

refs 2708

refs 2708

refs 2708

refs 2708

refs 2708

refs 2708

refs 2708

refs 2708

refs 2708

- Add TODO to change interface of IAnnotationValueProvider::getContextMenuEntries(): The method should be based on another method in IAnnotationValueProvider that returns a <String, BiConsumer> whose BiConsumer defines the action to apply to a single annotation entry. This ensures uniform iteration over the affected annotation entries, while providing the flexibility to enable custom iteration schemes
- Minor cleanup
  - Perform all modifications of an action in a single command
  - Re-update of annotation view only it was enabled before issuing the command 
refs 2361

- Add check box to toggle case sensitive match (default: insensitive match as before)

- Extend the IAnnotationValueProvider interface to include a method that returns a list of context menu entries with associated actions. The default implementation returns an empty list (implemented in the default interface method). This allows existing annotation value providers to add some default context menu actions by implementing an additional interface while existing AnnotationValueProviders do not need to be adjusted.
- Add an additional descriptor class "AnnotationInstSpec" that allows to uniquely identify the Annotation (& instanceKey) shown as columns in the annotation view. It has been abstracted from the class ColumnHandle.
- Add a method to the AnnotationLabelProvider that allows to query the Annotation for which it has been constructed.
- Extend the GenericAnnotationView to display a context menu for "annotation columns". The content of the context menu is specified by the AnnoationvalueProvider.
- Implement a context menu entry in the interface DefaultAnnotationContextActions that is implemented by the EnergyConsumptionValueProvider.
refs 2361

refs 2533

refs 2533

- In order to offer this functionality, the actions need to be integrated into the MenuManager by the concrete subclasses of TreeViewerEditorBase