refs 2154

- Performance optimization: Prevent reconstruction of identical column set (e.g., when only the selection or a value in the model is changed)
refs 1841

 - Cache annotation entries the different root elements. The cache for a given root element is invalidated when model elements are added to / removed from the structure beneath it.
 - Avoid superfluous updates:
   - Re-selection of a model element
   - ADD events for annotation objects. These are a caused by the addition of a model element which already triggers an ADD event.
refs 1841

Extends the Derived annotation, such that element-specfic values can be returned; Useful for aggregate annotations.
refs 2150

refs 2150

refs 2150

No commit message

- Fix bug that icon faking the native widget is not hidden when the actual widget is shown for editing
refs 1841

refs 2067

- Remove NOP override of setAnnotationValue()
refs 1841

refs 2154

- Adds support for checkboxes in the TableViewer (of the annotations). Still needs visual improvements.
- Modifies the GenericAnnotationView to support the checkbox-editing. 

- Ensure that currently selected model element is visible in table view (the change of the selection can be triggered in an external editor, e.g. the model navigator)
refs 1841,2137

- getValues(): cache AnnotationEntry list returned for given model element, significantly improving the performance of the AnnotationView for larger model. The view makes extensive use of this method from its update() method.
refs 1841

refs 1841

- Change semantics of SUB_MODEL scope declaration to also include the element to which the annotation is attached
- Preserve the current behavior (current element is not included) in STRICT_SUB_MODEL
refs 1841

- Cache column width (possibly manually adjusted by the user)
refs 1841

refs 1841

  - Broken after integration of EReference support since setting of values no longer defaults to String initializers)
  - Hence, also override doSetValue(AnnotationEntry, Object).
refs 1841

  - Contained features are created automatically by the generated EFactory
  - Non-contained features must be set by the user
-> Return null in any case
refs 1841

 - Rename computeFullyName() -> computeFullyQualifiedName()

 - Extend EStructuralFeatureValueProvider and ComboBoxEditingSupport to handle also this case
 - Reintroduce EStructuralFeatureDescriptor to provide means to specify the scope in which EReferences can be set
     - PROJECT: All models in the current project
     - MODEL: Current model (e.g., ComponentArchitecture)
     - SUB_MODEL: Sub-model below the model element that hosts the annotation managed by the current IAnnotationValueProvider
refs 1841

refs 1841

- Add constructor to DerivedAnnotationValueProviderBase that eases to build "mixed" annotations, i.e. those that provide one derived / calculated value, and one or more values backed by EStructuralFeatures
refs 1841

- If there is only one EStructuralFeature in the annotation's EClass, registered it with the DEFAULT_KEY
- This results in a more readable column heading (which is exactly the String returned by the user-supplied implementation of getAnnotationName(), instead of "<user-supplied String> : <EStructuralFeature name>"
refs 1841

- Unify (merge) MultiInstanceAnnotationSupport with (into) TextEditingSupport
refs 1841

- Add color code for uneditable annotations values
  - light gray: annotation does not exist for the given model elemnt
  - light blue: annotation is a derived / computed value
refs 1841

  Simply label it "Model Element"
- Likewise, in component filter, use "model element" instead of "component" as filter label
refs 1841

- In contrast to the implementation of EObjectAwareServiceBase.getRegisteredHandlers(Class), this implementation returns all IAnnotationValueProviders that have
been registered for the given class or any of its super-classes or interfaces.

- As a result, value providers may now be bound to different base classes of a given model element, e.g. for GenericECU, annotations that have been bound to ExecutionUnit and IPlatformArchitectureElement will be return (old behavior: only annotations bound to the nearest match, i.e. ExecutionUnit, would have been returned).

- TODO: Investigate if this behavior is also (optionally) desirable for other services and should be merged / integrated to EObjectAwareServiceBase.
refs 1841

refs 1841

refs 1841