Introduce "derived" annotation, i.e. based on calculations instead of explicit...
Introduce "derived" annotation, i.e. based on calculations instead of explicit annotations / model contents can be implemented - DerivedAnnotationBase meta-model element, with getValue() EOperation, and a extensive documentation. - Corresponding DerivedAnnotationValueProviderBase, implementing a read-only, text-view of the calculation result - To implement the above, move handling of annotation EClass & factory to ValueProviderBase refs 1841
Showing
- org.fortiss.tooling.base.ui/trunk/src/org/fortiss/tooling/base/ui/annotation/valueprovider/DerivedAnnotationValueProviderBase.java 66 additions, 0 deletions...ion/valueprovider/DerivedAnnotationValueProviderBase.java
- org.fortiss.tooling.base.ui/trunk/src/org/fortiss/tooling/base/ui/annotation/valueprovider/SingleEStructuralFeatureValueProviderBase.java 3 additions, 38 deletions...ueprovider/SingleEStructuralFeatureValueProviderBase.java
- org.fortiss.tooling.base.ui/trunk/src/org/fortiss/tooling/base/ui/annotation/valueprovider/ValueProviderBase.java 63 additions, 0 deletions...g/base/ui/annotation/valueprovider/ValueProviderBase.java
- org.fortiss.tooling.base/trunk/model/base.ecore 11 additions, 0 deletionsorg.fortiss.tooling.base/trunk/model/base.ecore
- org.fortiss.tooling.base/trunk/model/base.genmodel 3 additions, 0 deletionsorg.fortiss.tooling.base/trunk/model/base.genmodel
Please register or sign in to comment