- Mar 27, 2015
-
-
Johannes Eder authored
-
Vincent Aravantinos authored
refs 2122
-
- Mar 25, 2015
-
-
Simon Barner authored
- Add IAnnotationValueProvider.isHidden() that allows to hide annotations from any view (useful for internal attributes that should not be exposed to the user). Default = false - Extend AnnotationEntry and AnnotationFilter accordingly
-
- Mar 24, 2015
-
-
Simon Barner authored
-
Simon Barner authored
- Prevent pollution of AnnotationEntry <-> IModelElement cache via instantiateAnnotations(final IModelElement element) (which might be invoked from model transformations). I.e., the cache is only updated, when the AnnotationEntries are queried from the GUI context. - In case further measures need to be taken to limit the size of the AnnotationEntry <-> IModelElement cache, <http://stackoverflow.com/questions/2941283/java-fixed-memory-map> might be a good starting point
-
Simon Barner authored
-
Simon Barner authored
- Add RemoveUnknownFeatureMigrationProviderBase, a base class for {@link IMigrationProvider}s to selectively remove unknown features from a model.
-
- Mar 18, 2015
-
-
Simon Barner authored
- Instead of iteration over the entire model for each IIdLabeled element whose ID is to be checked for consistency and uniqueness, register the constraint checker for the FileProject and do each of the checks in one pass. - Should fixes drastic performance problems introduced with last change to resolve this issue refs 2309
-
- Mar 17, 2015
-
-
Simon Barner authored
- Add prefix "generated-" for directories of generated edit and editor code (not used in default AF3 distribution)
-
Simon Barner authored
- By default, EMF uses fragment-path based links to persist EReferences. While this works fine for standalone model resources, it can cause inconsistencies in case there are multiple resource models that contain cross-resource references. (I.e., if the structure of the AF3 model resource changes, the links from the external model resource can become invalid) - The recommended way to work around this is to configure EMF to use IDs to encode EReferences. Solution: - Change persistence of AF3 model resources to encode references using an (extrinsic) xmi:id, that is identical to the model element's org.fortiss.tooling.kernel.model.IIdLabled.id. A dedicated XMIResource type for AF3 model resources is used (which is created by a resource factory registered for *.af3_23 files) - The reason for not using IIdLabled.id as intrinsic ID is that the implemented solution using xmi:id is both forward and backward compatible - At the price of losing forward compatibility, the IIdLabled.id could be changed to a derived, volatile EAttribute that simply returns the value of xmi:id - Add EContentAdapter to sync xmi:id and IIdLabled.id - Ensure uniqueness of IDs (that is now much more crucial) during when loading and saving as well as importing and exporting models (and print a warning to the console in case duplicates have been detected and fixed) - As an additional safety layer, add constraint checkers to ensure uniqueness of IDs and consistency of IIdLabled.id and xmi:id Related changes: - Speed up loading and saving of XMI resources by setting corresponding XMLResource options - Ensure that IDs are assigned to annotations as soon as they are instantiated refs 2309
-
- Mar 16, 2015
-
-
Simon Barner authored
- GSNPositionedEditPartBase*: Avoid code duplication by pushing refreshDecorationFigure() to PositionedEditPartBase - PositionedEditPartBase.refreshDecorationFigure() - Avoid SWT Image leak by reusing the same icons - Add more null-checks to implementation - MarkerViewPart -> column updater: Avoid SWT Image leak by disposing old image before setting a new one
-
Simon Barner authored
- Undo last two changes: will be handled by ElementCompositorService (in the kernel) refs 2309
-
- Mar 12, 2015
-
-
Simon Barner authored
refs 2309
-
Simon Barner authored
- Assign unique IDs to annotations as soon as the are instantiated (before, annotations relied on the ID-fixup that is triggered when the model is persisted) refs 2309
-
- Feb 23, 2015
-
-
Simon Barner authored
- Keep order of elements to be selected (e.g., EENum values) etc. by using a LinkedHashMap instead of a TreeMap
-
Simon Barner authored
-
Alexander Diewald authored
Fixes a bug in the EStructuralFeatureValueProvider that caused the Enum filter list to be applied on objects that should not be filtered.
-
Alexander Diewald authored
Adds the possibility to filter the list of available choices for an enum-type annotation via the annotation's value provider. Therefore, a map containing the class of the to be filtered model elements and the allowed enum literal must be given in the constructor of the value provider.
-
- Feb 20, 2015
-
-
Simon Barner authored
-
- Feb 16, 2015
-
-
Simon Barner authored
DerivedAnnotationValueProviderBase.setAnnotationValue(): Convert String-encoded input to actual data type
-
Simon Barner authored
-
- Feb 12, 2015
-
-
Simon Barner authored
refs 2240
-
Simon Barner authored
refs 2226
-
Simon Barner authored
-
Simon Barner authored
-
Simon Barner authored
refs 2289
-
Simon Barner authored
generalize RequirementSpecificationUtils.removeRequirementSpecifications() to BaseModelElementUtils.removeModelElementReferenceSpecifications() refs 2240
-
- Feb 09, 2015
-
-
Vincent Aravantinos authored
refs 2140
-
Simon Barner authored
-
- Feb 06, 2015
-
-
Vincent Aravantinos authored
-
Simon Barner authored
refs 2255
-
- Feb 05, 2015
-
-
Vincent Aravantinos authored
refs 2255
-
Vincent Aravantinos authored
refs 2255
-
Vincent Aravantinos authored
refs 2255
-
Vincent Aravantinos authored
refs 2255
-
Vincent Aravantinos authored
refs 2255
-
Simon Barner authored
refs 2255
-
Vincent Aravantinos authored
refs 2255
-
Vincent Aravantinos authored
refs 2255
-
Vincent Aravantinos authored
refs 2255
-