-
Simon Barner authored
- Move annotation value service, annotation value provider base classes and annotation extension point to org.foritss.tooling.base - Remove createEditingSupport() from IAnnotationValueProviderBase and move functionality to org.fortiss.tooling.base.ui.annotation.editingsupport.EditingSupportFactory instead - Rename extension point to org.fortiss.tooling.base.annotation. Example binding: <extension point="org.fortiss.tooling.base.annotation"> <annotation binding="org.fortiss.af3.timing.annotation.valueprovider.CIValueProvider"> <modelElementClass modelElementClass="org.fortiss.af3.component.model.Component"/> </annotation> </extension - Adapt all known users of annotation framework to new structure - The change is a preparation to fix #2208, i.e. to put the instantiation of a model element and its annotations into a single undo/redo command refs 2208
Simon Barner authored- Move annotation value service, annotation value provider base classes and annotation extension point to org.foritss.tooling.base - Remove createEditingSupport() from IAnnotationValueProviderBase and move functionality to org.fortiss.tooling.base.ui.annotation.editingsupport.EditingSupportFactory instead - Rename extension point to org.fortiss.tooling.base.annotation. Example binding: <extension point="org.fortiss.tooling.base.annotation"> <annotation binding="org.fortiss.af3.timing.annotation.valueprovider.CIValueProvider"> <modelElementClass modelElementClass="org.fortiss.af3.component.model.Component"/> </annotation> </extension - Adapt all known users of annotation framework to new structure - The change is a preparation to fix #2208, i.e. to put the instantiation of a model element and its annotations into a single undo/redo command refs 2208