[Kernel] Add LWFXEF framework from SystemFOCUS to kernel.common.ui

(from redmine: issue id 3815, created on 2019-09-09, closed on 2020-02-04)

• Relations:
  • relates #3843 (closed)
  • child #2751 (closed)
  • child #3003 (closed)
  • child #3870 (closed)
  • parent #3878 (closed)

added Type::Feature + 1 deleted label

Testing and intermediate code review done. Please see the branches for / gitlab for the code review comments.

Here is what I found during testing except the known bugs (DnD from the library):

• Double-clicking a component to open the editor of its content is not working.
• Components can only be moved after selecting them.
• Ports added to a component only become visible after adding a port to the pane (parent component). In the SWT view, the components added in the FX view are visible.
• Connection endpoints are misaligned.
• Sometimes connections cannot be drawn at all (with the Input / Output port restrictions considered). Did not yet find a pattern causing this behavior.
• Ports are not moved when their parents are resized. Thus, they may be “outside” the component to which they belong depending on the resize operation.

(from redmine: written on 2019-11-14)

Intermediate merge is done:

• target-definition!5 (merged)
• kernel!74 (merged)
• https://git.fortiss.org/af3/af3/merge_requests/260

All issues noted before are resolved now.

(from redmine: written on 2019-11-19)

changed milestone to %AF3 2.17 (Feature Freeze)

SF code has been integrated into AF3 Kernel.

(from redmine: written on 2020-02-04)

Please reevaluate the issues:

• Double-clicking a component to open the editor of its content is not working.
• Components can only be moved after selecting them.
• Ports added to a component only become visible after adding a port to the pane (parent component). In the SWT view, the components added in the FX view are visible.
• Connection endpoints are misaligned.
• Sometimes connections cannot be drawn at all (with the Input / Output port restrictions considered). Did not yet find a pattern causing this behavior.
• Ports are not moved when their parents are resized. Thus, they may be “outside” the component to which they belong depending on the resize operation.

(from redmine: written on 2019-11-19)

closed

mentioned in issue #3843 (closed)

mentioned in issue #3870 (closed)

mentioned in issue #3878 (closed)

mentioned in issue #3927 (closed)