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

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


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

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


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

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


Signed-off-by: Alexander Diewald <diewald@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: 3538
Signed-off-by: Alexander Diewald <diewald@fortiss.org>

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

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

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

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



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

Issue-Ref:3401

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

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



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

* Add an abstract method for "initialize()".
* Fixed comments.

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


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

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

* Modify the constructors such that AF3FXViewParts can be created
  that only contain a single FX node/control, and do not come along
  with a FXML layout file.
* Due to signature conflicts, the css location must be given in the
  constructor. The default case is to use "null" such that the
  OS-native look is used.
* Add a method "setChildNodeFinal" that must be used to add the FX node
  to the view. It is not possible to do this in constructors since the
  FX toolkit is not initialized at this point in time.

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


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

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

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

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


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

* Create an additional constructor that allows passing a TreeTableView,
  which has been constructed/injected beforehand. It is a requirement
  to use this simplification in combination with FXML.

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


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

* Adjusts the settings in the Windows 10 CSS.
* Rows are hard to see without this change.

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


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

* The UI provider operates on the items passed by the updateItem method
  in the DynamicTreeViewer.
* Avoid the required null-checks in the UI providers by moving this
  check to the Viewer. This reduces the boilerplate code.

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


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

* In order to allow dynamic filling of the eclipse views, don't set a
  fixed Scene size to allow dynamic resizing as required.

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


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

* DynamicTreeViewers and alike are often used for a specific set of base
  types. Thus, generics can be used to reduce the code by subclassing
  these controls for specific meta-model types like IHierarchicElements.
* Second, a bit more type-safety is achieved without sacrificing
  ease-of-use since the controls can still be constructed for Objects
  for complex object relations.

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


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

* Taken from the SystemFOCUS project.
* Initial import that is lacking integration in the SWT-JavaFX
  "framework".
* Integration with the "framework" and FXML is done in separate commits
  to decouple the import from the integration work.

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


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

* Add style sheets for a native look of JavaFX-based views such that the
  UI does not break too much in comparison to the SWT-based views.
* Windows 8/10, Windows 7, and MacOS X are supported. For Linux (GTK/QT)
  no style sheets have been found at the creation time of this commit.
* The style sheets for the Windows 7 and the MacOS look are bundled in
  jars that define additional controls for animation etc. These libs
  are not usable with the SWT/JavaFX integration layer since it is
  impossible to load the control classes defined in the CSS file. The
  reason for this resides in the special classloader architecture of the
  JavaFX/SWT integration where it is impossible to inject classes into
  the classloader hierarchy without modifying e(fx)clipse plugins, or
  writing custom classloader/wrapper plugins for osgi.
* The licenses of the imported CSS files are 2- and 3-clause BSD
  licenses which are placed in the folders containing the CSS files.

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


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

* Since the tooling helpers used in the svn installation and the git
  version, a re-rating of all files was required (less work than fixing
  the tooling code that would be only used once).
* Updates the hashes of the classes in the .rating files.
* Removes empty .rating files from directories without ratable files.

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

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

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

refs 3241

refs 3249

refs 3241

are marked as @Deprecated //ucd
refs 3240

refs 3209

refs 3209

refs 3217

refs 3217