3598: EcoreUtils::copyToRefMap

See merge request !43

3319: Service Registrations : Handle ambiguity caused by generated EMF "Impl" types

See merge request !44

Issue-Ref: 3319
Issue-Url: https://af3-developer.fortiss.org/issues/3319


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3598
Issue-Url: https://af3-developer.fortiss.org/issues/3598



Signed-off-by: Tiziano Munaro <munaro@fortiss.org>

* Method to create a self-contained copy of the given EObject.
* It returns a Map that relates each original sub-element (including
  the given EObject) to the corresponding copy.

Issue-Ref: 3598
Issue-Url: https://af3-developer.fortiss.org/issues/3598



Signed-off-by: Simon Barner <barner@fortiss.org>

3470 timing model

See merge request !39

Issue-Ref: 3470
Signed-off-by: ponce <ponce@fortiss.org>

3267: Support for multivalued (non-EReference) annotations

See merge request !42

* Just fixed a few comments.

Issue-Ref: 3267
Issue-Url: https://af3-developer.fortiss.org/issues/3267



Signed-off-by: Marco Volpe <volpe@fortiss.org>

Issue-Ref: 3578
Issue-Url: https://af3-developer.fortiss.org/issues/3578



Signed-off-by: Marco Volpe <volpe@fortiss.org>

* For a given EClass "Foo", the map considers the generated interface
  class "Foo" and the corresponding implementation class "FooImpl"
  identical.

Issue-Ref: 3319
Issue-Url: https://af3-developer.fortiss.org/issues/3319



Signed-off-by: Simon Barner <barner@fortiss.org>

CR: GREEN

See merge request !41

Moved the abstract source editor to tooling base.

See merge request !40

Issue-Ref: 3536
Issue-Url: https://af3-developer.fortiss.org/issues/3536


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3536
Signed-off-by: Sudeep Kanav <kanav@fortiss.org>

Issue-Ref: 3536
Signed-off-by: Sudeep Kanav <kanav@fortiss.org>

Issue-Ref: 3536
Signed-off-by: Sudeep Kanav <kanav@fortiss.org>

* Add new classes
  * MultiValueAnnotationTextEditingSupport, an editing support that
    allows for textual editing of multi-value annotation.
  * MultiValueAnnotationTextEditingDialog, a dialog to that allows to
    edit multiple values
* Adapt
  * EditingSupportFactory to instantiate
    MultiValueAnnotationTextEditingSupport instead of throwning an
    exception about an unsupported case
  * EStructuralFeatureValueProviderBase to set values using the new
    method setAnnotationValueFromString(Collection<String>, T)

Issue-Ref: 3578
Issue-Url: https://af3-developer.fortiss.org/issues/3578



Signed-off-by: Simon Barner <barner@fortiss.org>

* Editing support: IMultiValueAnnotationEditingSupport with base class
   MultiValueAnnotationEditingSupportBase
    * currently used in MultiValueAnnotationSelectionEditingSupport
    * integrates cell editor (whose updateData() has been dropped in
      favor of the constructor, i.e. a new cell editor is created each
      time
* Dialogs: IMultiValueAnnotationDialog with base class
  MultiValueAnnotationDialogBase
  * currently used by MultiValueAnnotationSelectionDialog

Issue-Ref: 3267
Issue-Url: https://af3-developer.fortiss.org/issues/3267



Signed-off-by: Simon Barner <barner@fortiss.org>

* Red: Namings in CustomUndoRedoForSourceEditor, SourceEditorBase.
* GREEN: annotations.

Issue-Ref: 3582
Issue-Url: https://af3-developer.fortiss.org/issues/3582


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3536
Signed-off-by: Sudeep Kanav <kanav@fortiss.org>

3470-timing_model

Conflicts:
	org.fortiss.tooling.kernel.ui/src/org/fortiss/tooling/kernel/ui/extension/base/.ratings
	org.fortiss.tooling.kernel.ui/src/org/fortiss/tooling/kernel/ui/internal/properties/.ratings


Signed-off-by: Simon Barner <barner@fortiss.org>

Double input format validation: check if the entire string was parsed

See merge request !38

Issue-Ref: 3582
Issue-Url: https://af3-developer.fortiss.org/issues/3582


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

* Fixes a problem introduced in during the synchronization of the
  selection of the model editor and the model navigator (in #3084)

Issue-Ref: 3470
Issue-Url: https://af3-developer.fortiss.org/issues/3470



Signed-off-by: Simon Barner <barner@fortiss.org>

* No longer depend on org.conqat.ide.commons.ui.databinding.validate.*
* Improve NumberFormat validation
  * Do not accept if input contains a valid prefix
  * Provide more precise error message
  * Do not accept (1000er) grouping separator (in order to avoid
    confusion with decimal separator
* PropertySectionBase
  * Use updated validators
  * For BigDecimals, avoid introducing grouping separators during
    value -> String conversion

Issue-Ref: 3582
Issue-Url: https://af3-developer.fortiss.org/issues/3582



Signed-off-by: Simon Barner <barner@fortiss.org>

* Creates a Text widget (with undo) and adds ControlDecoration
* "Label createDecoratedFormText()" retains the previous semantics of
  these methods, i.e. it wraps the created Text into a form entry

Issue-Ref: 3582
Issue-Url: https://af3-developer.fortiss.org/issues/3582



Signed-off-by: Simon Barner <barner@fortiss.org>

Issue-Ref: 3582
Issue-Url: https://af3-developer.fortiss.org/issues/3582



Signed-off-by: Simon Barner <barner@fortiss.org>

Issue-Ref: 3582
Issue-Url: https://af3-developer.fortiss.org/issues/3582



Signed-off-by: Simon Barner <barner@fortiss.org>

* Rename singleton instance to NUMBER_VALIDATOR
* Use java.text.NumberFormat instead of the one from com.ibm.icu
* Disallow using 1000er group separator into to avoid confusions
  with decimal separator
* Accept empty input, as well as leading and trailing spaces

Issue-Ref: 3582
Issue-Url: https://af3-developer.fortiss.org/issues/3582

* Retain almost all ratings ratings
* Exception: AbstractTextCellDatabindingEditingSupport, whose
  setupFieldAssist() method was removed since
   * it would have introduced a dependency to another package in
     base.ui only because is "FieldAssist" class was referenced in
     the method *comment*.
   * However, this method is only used very rarely and users of the
     class setup up their field assist in createCellEditor() instead.

Issue-Ref: 3582
Issue-Url: https://af3-developer.fortiss.org/issues/3582



Signed-off-by: Simon Barner <barner@fortiss.org>

* setEnabled(false) in createControls() has no effect, i.e. the text
  can be edited, but the change is not saved in the model. In refresh(),
  it  would have an effect, but would "gray out" the text control
* setEditable(false) prevents the user from entering text in the
  first place.

Issue-Ref: 3582
Issue-Url: https://af3-developer.fortiss.org/issues/3582



Signed-off-by: Simon Barner <barner@fortiss.org>