refs 2885

refs 2779

- Check each pasted referenced element if it can be pasted to the target annotation.
refs 2361

Add a utility method to get the directly connected elements of a given IHierarchicElement that have the given type.

- Add a migration util method for IAnnotatedSpecifications.
- Documentation cleanup.
- Minor refactoring.

- Copy operation are not dirtying the model any more: Add a write flag to annotation actions; Only those will are dirtying a model now.
- Context menu in the annotation view is no longer visible for non-editable annotations.
- References and multi-references are now correctly handled:
  - Correct the set logic.
  - Offer two kinds of pastes for multi-reference annotations: append, replace.
- Fix duplicated context menu entries for the SafetyIntegrityLevel annotation (details: see bug report).
refs 2361

- Move the getEStructuralFeatureDescriptor method to the IAnnotationValueProvider interface.
- Move the getContectMenuEntries method for AnnotationValueProviders to the ValueProviderBase class.
  - Remove the DefaultAnnotationContextActions interface that provided a default implementation.
  - Add copy & paste Actions to the ValueProviderBase class.
- Improve the handling of (Annotation) instanceKeys in the GenericAnnotationView.
- Generalize the Action to create random values for the annotations of the visible element set in the annotation view:
  - Can handle only Number types up to now.
  - Add a static method in AnnotationUtils that allows to provide this capability in AnnotationValueProviders.
- Add a BaseMathUtils utility class in org.fortiss.tooling.base to handle "dynamic" Number conversions that are not considered in Apache common's MathUtils: Used, e.g., for the randowm number generation.
- Update the EnergyConsumption- & WcetValueProviders.
refs 2361

refs 2653

- This will be performed by the IElementCompositorService that is called from createNewSourceDropContext().
- Doing it here already, will trigger an expensive check for duplicate IDs when the ID assignment is issued for the second time from the IElementCompositorService
refs 2759

- I.e., do this for each specification instead of the "contained" model element. Since
"contained" might already have an any, this would trigger an expensive algorithm to
check if there are duplicated IDs.
refs 2759

- prepareAnnotationEntry(): Comment out warning in case the annotation has not been instantiated yet. In the current situation, it has a performance impact on model transformations.
refs 2228

- prepareAnnotationEntry(): Emit a warning in case the annotation has not been instantiated yet. The goal is to remove the code that instantiates the annotation on the fly in the long run.
refs 2228

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 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 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

- 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

refs 1119

- For reasons of consistency, and to avoid that "generated-src" directory is deleted by IDE dev tools' EcoreBuilder, start specification of directory for generated edit code with a '/' (just like the model, editor, and test code directories)
refs 1119

refs 2490

refs 2490

refs 2490

refs 2572

refs 631

refs 2490