Ulrich Schöpp authored 3 years ago and Ulrich Schöpp committed 3 years ago

Signed-off-by: Ulrich Schöpp <schoepp@fortiss.org>
Issue-Ref: 3872

Issue-Ref: 4167

Signed-off-by: Johannes Eder <eder@fortiss.org>

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



Signed-off-by: Johannes Eder <eder@fortiss.org>

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



Signed-off-by: Johannes Eder <eder@fortiss.org>

Completely replaced the old annotation view with the fx based
implementation.
So far, both were available in parallel.

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


Signed-off-by: Andreas Bayha <bayha@fortiss.org>

First Durchstich to display annotations according to the current
selection.

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


Signed-off-by: Andreas Bayha <bayha@fortiss.org>

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


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

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


Signed-off-by: Florian Hoelzl <hoelzl@fortiss.org>

* Only use delegate factories in the FX editor base. By that all editors
  are extensible.
* Move the definition of the factories of one editor from the editor to
  its bindings.
* Create the concrete factories by reflection when a FX editor is
  constructed.

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


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

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


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

* For Connectors & Links.
* Add a controller for HierarchicElements.

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


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

* Move fx-base classes dealing with controllers to a dedicated package
  to prepare adding more base classes.
* Place type checks in the constructors of AF3 base classes to avoid
  them in the large set of concrete classes.
* Transform several base classes to classes such that they can be
  directly instantiated by factories if no specialization is needed.

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


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

* removed all constraint classes

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



Signed-off-by: Johannes Eder <eder@fortiss.org>

Base classes for standard boxes-and-wires diagram have been introduces
in order to avoid code duplication among similar diagram types.

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



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

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


Signed-off-by: Florian Hoelzl <hoelzl@fortiss.org>

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

Issue-Ref: 3725
Signed-off-by: Hernan Ponce de Leon <ponce@fortiss.org>

* Refer to the modular JDK-11 in the classpath.
* Depend on openjfx plugins from Tom Schindl.

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


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

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

* 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>

Signed-off-by: reaboi <reaboi@fortiss.org>

Signed-off-by: Florian Hoelzl <hoelzl@fortiss.org>

* Add a TreeViewer that constructs a DynamicTreeViewer whose UI provider
  uses the methods and kernel services for IHierarchicElements and
  NamedElements.
* The Viewer uses a composition principle where a client must provide
  TreeView (JavaFX), a root element (AF3), and a content provider that
  selects the elements to be displayed.
* Add two basic content providers that a) list all children below the
  given root element and b) list all children of a given type.

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


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

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