AF3 issueshttps://git.fortiss.org/af3/af3/-/issues2023-01-26T13:48:00Zhttps://git.fortiss.org/af3/af3/-/issues/4144AnnotationView / DynamicTextFieldTreeTableCell: Avoid exception when losing f...2023-01-26T13:48:00ZSimon BarnerAnnotationView / DynamicTextFieldTreeTableCell: Avoid exception when losing focus (but apply value)Steps to repeat
- Open ACC example
- Open Task Architecture
- Change "Flash size" annotation of any Task
- Click on Component Architecture
- Observe error box stating a "Problem during setting an AnnotationValue" (stemming from ``org.fo...Steps to repeat
- Open ACC example
- Open Task Architecture
- Change "Flash size" annotation of any Task
- Click on Component Architecture
- Observe error box stating a "Problem during setting an AnnotationValue" (stemming from ``org.fortiss.tooling.base.ui.annotation.view.fx.AnnotationViewFXController.setAnnotationEntryValue()``
Note that annotation values are applied only when clicking into an annotation view row of a different model element. Otherwise, a the text edit field remains opened, the value is not applied, and the problem above will arise when clicking somewhere else.![annotation-edit-error](/uploads/f352f394e60f22ef7c3e59288430ea67/annotation-edit-error.PNG)Backloghttps://git.fortiss.org/af3/af3/-/issues/4136Improved useability for connections in logical architecture2023-01-26T09:45:41ZAndreas BayhaImproved useability for connections in logical architectureAt the moment, the fx editor for the logical architecture does only permit to connect (existing) OutputPorts with InputPorts.
The useability of this editor could be improved by adding the following possibilities:
- [ ] Input<-Output (st...At the moment, the fx editor for the logical architecture does only permit to connect (existing) OutputPorts with InputPorts.
The useability of this editor could be improved by adding the following possibilities:
- [ ] Input<-Output (start dragging from an input port)
- [ ] Component -> InputPort (output port is automatically created)
- [ ] OutputPort -> Component (input port is automatically created)
- [ ] Component -> Component (both ports are automatically created)
Part of this issue is to evaluate how much effort it would be to implement each of these options. Based on this estimation a decision shall be made which options shall actually implemented.
This Implementation of SystemFocus might be reused or at least be helpful:
https://git.fortiss.org/systemfocus/upstream-clone/-/blob/master/bundles/org.eclipse.systemfocus.examples.function.architecture/src/org/eclipse/systemfocus/examples/function/architecture/compositors/connection/PortToPortConnectionCompositor.javaBackloghttps://git.fortiss.org/af3/af3/-/issues/4091Enable multiselect context menus for JFX Tables/Graphical Editors and adapt A...2023-01-26T10:16:36ZAlexander DiewaldEnable multiselect context menus for JFX Tables/Graphical Editors and adapt AF3 implementationsIn AF3, a context menu service exists such that each plugin can add contributors to the context menu of model elements. This service also handles multiselections.
For TreeViewers, the support shall be implemented in #3922.
However, for...In AF3, a context menu service exists such that each plugin can add contributors to the context menu of model elements. This service also handles multiselections.
For TreeViewers, the support shall be implemented in #3922.
However, for JFX-based tables and Graphical Editors, the support is for the service to build context menus is missing. To resolve the ticket, it must be clarified if the context menu service shall be used in future at all (and all context menu contributions must be migrated). If so, the base class for tables "DynamicTreeTableViewer" and the corresponding factories of the graphical editor elements must be adjusted.Backloghttps://git.fortiss.org/af3/af3/-/issues/4044Simulation OperatorPanels to JavaFX2023-01-26T10:15:21ZJohannes EderSimulation OperatorPanels to JavaFXTransformation of the Simulation Operator Panels
(org.fortiss.af3.operatorpanel.ui) to JavaFX.
*(from redmine: issue id 4044, created on 2020-07-20)*
* Relations:
* child #4082Transformation of the Simulation Operator Panels
(org.fortiss.af3.operatorpanel.ui) to JavaFX.
*(from redmine: issue id 4044, created on 2020-07-20)*
* Relations:
* child #4082Backloghttps://git.fortiss.org/af3/af3/-/issues/4013[UI] Collection task SWT based views -> JavaFX-based views2023-01-26T09:41:20ZJohannes Eder[UI] Collection task SWT based views -> JavaFX-based views
*(from redmine: issue id 4013, created on 2020-05-12)*
* Relations:
* child #3434
* child #3922
* child #4014
* child #4015
* child #4016
* child #4017
* child #4018
* child #4019
* child #4020
* child #4075
*(from redmine: issue id 4013, created on 2020-05-12)*
* Relations:
* child #3434
* child #3922
* child #4014
* child #4015
* child #4016
* child #4017
* child #4018
* child #4019
* child #4020
* child #4075Backloghttps://git.fortiss.org/af3/af3/-/issues/3988MIRA: Validator duplicated IDs in FX editor2023-01-16T14:19:17ZAndreas BayhaMIRA: Validator duplicated IDs in FX editorThe validator is still pending.
See parent issue \#3940
*(from redmine: issue id 3988, created on 2020-04-03)*
* Relations:
* parent #3940The validator is still pending.
See parent issue \#3940
*(from redmine: issue id 3988, created on 2020-04-03)*
* Relations:
* parent #3940BacklogAndreas BayhaAndreas Bayhahttps://git.fortiss.org/af3/af3/-/issues/3957Improve Glossary integration2023-01-16T14:17:14ZAndreas BayhaImprove Glossary integrationThe Glossary implementation used to be more suffisticated in swt. Some
features could not yet be reimplemented, since the fx integration does
not yet support it.
This includes:
- Highlight Glossary terms when they are used in text fie...The Glossary implementation used to be more suffisticated in swt. Some
features could not yet be reimplemented, since the fx integration does
not yet support it.
This includes:
- Highlight Glossary terms when they are used in text fields as
requirements, comments etc.
- Add possibilitiy to right-click on words in text fields as
requirements, comments, etc to add them to the glossary.
- Autocompletion for glossary entries in text fields
*(from redmine: issue id 3957, created on 2020-03-20)*Backloghttps://git.fortiss.org/af3/af3/-/issues/3952Color contrast in some JavaFX diagram editors is very low2023-04-03T07:22:49ZSimon BarnerColor contrast in some JavaFX diagram editors is very lowThe task of this ticket is to go through all diagram editors and to
check if the labels of all model elements are readable (by instantiating
all model elements in a test model).
See attachment for an example.
Possible resolution: make ...The task of this ticket is to go through all diagram editors and to
check if the labels of all model elements are readable (by instantiating
all model elements in a test model).
See attachment for an example.
Possible resolution: make background color lighter, use brighter font
color (white?)
*(from redmine: issue id 3952, created on 2020-03-17)*
* Uploads:
* ![Image_Pasted_at_2020-3-17_15-44](/uploads/b32d1f04b4da92a1da30975bfdc24e99/Image_Pasted_at_2020-3-17_15-44.png)AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/3937MIRA: Display images in FX editor2023-01-16T14:21:21ZAndreas BayhaMIRA: Display images in FX editorThe FX Editor currently does not display images.
I won’t be able to reimplement this feature until the feature freeze…
*(from redmine: issue id 3937, created on 2020-02-28)*The FX Editor currently does not display images.
I won’t be able to reimplement this feature until the feature freeze…
*(from redmine: issue id 3937, created on 2020-02-28)*Backloghttps://git.fortiss.org/af3/af3/-/issues/3936Data State (FX) editor: Show elements of arrays and structs as children of th...2023-01-26T10:51:03ZDummy AF3-DevData State (FX) editor: Show elements of arrays and structs as children of the respective variablesWhile easily editable, the current textual representation of arrays and
structs in the data state (FX) editor is not suitable for handling
larger data structures.
A more clear way to display such data and operate on it would be to
incl...While easily editable, the current textual representation of arrays and
structs in the data state (FX) editor is not suitable for handling
larger data structures.
A more clear way to display such data and operate on it would be to
include the elements of a structure in the tree table view as children.
This representation is also consistent with the data dictionary.
*(from redmine: issue id 3936, created on 2020-02-26)*
* Relations:
* relates #3909Backloghttps://git.fortiss.org/af3/af3/-/issues/3922ModelNavigatorView to JavaFX2023-03-23T15:47:55ZJohannes EderModelNavigatorView to JavaFXCreation of a new JavaFX-based ModelEditorView in order to replace the
old SWT-based implementation. The view shall be similar to the old one,
hence control code may be reused.
*(from redmine: issue id 3922, created on 2020-01-27)*
* ...Creation of a new JavaFX-based ModelEditorView in order to replace the
old SWT-based implementation. The view shall be similar to the old one,
hence control code may be reused.
*(from redmine: issue id 3922, created on 2020-01-27)*
* Relations:
* relates #4019
* relates #4076
* parent #4013BacklogJohannes EderJohannes Ederhttps://git.fortiss.org/af3/af3/-/issues/3919SourceEditorBase<T> to JavaFX2023-01-26T10:10:22ZJohannes EderSourceEditorBase<T> to JavaFXCreation of a new JavaFX-based SourceEditorBase<T> (+
CodeSpecificationEditor) in order to replace the old SWT-based
implementation. The editor shall be similar to the old one, hence
control code may be reused.
*(from redmine: issue id...Creation of a new JavaFX-based SourceEditorBase<T> (+
CodeSpecificationEditor) in order to replace the old SWT-based
implementation. The editor shall be similar to the old one, hence
control code may be reused.
*(from redmine: issue id 3919, created on 2020-01-27)*
* Relations:
* parent #3906Backloghttps://git.fortiss.org/af3/af3/-/issues/3917ArchitecureParameterEditorBase<A,T> to JavaFX2023-01-26T15:32:19ZJohannes EderArchitecureParameterEditorBase<A,T> to JavaFXCreation of a new JavaFX-based
ArchitectureParameterEditorBase&lt;A,T>in order to replace the old
SWT-based implementation. The editor shall be similar to the old one,
hence control code may be reused.
*(from redmine: issue id 3917, cr...Creation of a new JavaFX-based
ArchitectureParameterEditorBase<A,T>in order to replace the old
SWT-based implementation. The editor shall be similar to the old one,
hence control code may be reused.
*(from redmine: issue id 3917, created on 2020-01-27)*
* Relations:
* parent #3906BacklogSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/3915ModelListenerEditorBase<T> to JavaFX2023-03-29T07:08:02ZJohannes EderModelListenerEditorBase<T> to JavaFXCreation of a new JavaFX-based ModelListenerEditorBase<T> in order to
replace the old SWT-based implementation. The editor shall be similar to
the old one, hence control code may be reused.
*(from redmine: issue id 3915, created on 202...Creation of a new JavaFX-based ModelListenerEditorBase<T> in order to
replace the old SWT-based implementation. The editor shall be similar to
the old one, hence control code may be reused.
*(from redmine: issue id 3915, created on 2020-01-27)*
* Relations:
* parent #3906BacklogSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/3906[UI] Collection task to switch SWT based editors to the new JavaFX-based editors2023-10-23T07:24:49ZJohannes Eder[UI] Collection task to switch SWT based editors to the new JavaFX-based editors
*(from redmine: issue id 3906, created on 2020-01-27)*
* Relations:
* child #3907
* child #3908
* child #3909
* child #3910
* child #3911
* child #3912
* child #3913
* child #3914
* child #3915
* child #3916
* c...
*(from redmine: issue id 3906, created on 2020-01-27)*
* Relations:
* child #3907
* child #3908
* child #3909
* child #3910
* child #3911
* child #3912
* child #3913
* child #3914
* child #3915
* child #3916
* child #3917
* child #3918
* child #3919
* child #3920
* child #3921
* child #3939Backloghttps://git.fortiss.org/af3/af3/-/issues/3899[UI] Introduce JavaFX-based code specification editor2023-01-17T15:10:41ZDummy AF3-Dev[UI] Introduce JavaFX-based code specification editorRe-implement
`org.fortiss.af3.component.ui.editor.CodeSpecificationEditor` using
JavaFX.
*(from redmine: issue id 3899, created on 2019-12-16)*Re-implement
`org.fortiss.af3.component.ui.editor.CodeSpecificationEditor` using
JavaFX.
*(from redmine: issue id 3899, created on 2019-12-16)*BacklogTiziano MunaroTiziano Munarohttps://git.fortiss.org/af3/af3/-/issues/3898[LWFXEF] More options for javafx editors2023-03-10T16:07:52ZDummy AF3-Dev[LWFXEF] More options for javafx editorsMore options are needed in order to match the previous UI.
This issue complement \#3889 which refers only to text.
\- Allow fixed colors to fill an element. See e.g. platform architecture
in the old UI. ECUs are green/yellow, buses ar...More options are needed in order to match the previous UI.
This issue complement \#3889 which refers only to text.
\- Allow fixed colors to fill an element. See e.g. platform architecture
in the old UI. ECUs are green/yellow, buses are green/white
\- Allow to change the position of the icon. Currently I managed center
the text (name) of a rectangle, but the icon remains always on the left.
\- Allow to “decorate” rectangles. E.g. in the old UI, generic ECUs have
dots in the corners
\- Allow to create a channel by selecting the input connector and moving
to mouse to the output connector.
\- Allow to reconnect a link: i.e. change the end-point of a link
- Allow to move an existing connector using the keyboard arrows.
Currently it works for rectangles, but not for anchors.
*(from redmine: issue id 3898, created on 2019-12-10)*
* Relations:
* duplicates #3889Backloghttps://git.fortiss.org/af3/af3/-/issues/3889[LWFXEF] Add more options for adding, modifying and displaying text2023-03-10T16:08:03ZDummy AF3-Dev[LWFXEF] Add more options for adding, modifying and displaying text- Add getters and setters for text properties such as color and font
weight within the `ContentVisualBase`.
- Handle text overflow with dots instead of line breaks.
- Allow text to be added to anchorages (such as single charact...- Add getters and setters for text properties such as color and font
weight within the `ContentVisualBase`.
- Handle text overflow with dots instead of line breaks.
- Allow text to be added to anchorages (such as single characters like
‘S’ and ‘Q’ to distinguish sampling ports from queuing ones).
*(from redmine: issue id 3889, created on 2019-12-06)*
* Relations:
* duplicates #3898Backloghttps://git.fortiss.org/af3/af3/-/issues/3877[UI] Move type checks and casts from LWFXEF visuals to a common base class wi...2023-03-10T16:09:23ZDummy AF3-Dev[UI] Move type checks and casts from LWFXEF visuals to a common base class within SystemFocusChecks of the type
```java">
object model = mvcb.getmodel();
if(!(model instanceof ilayoutedmodelelement)) {
throw new illegalargumentexception(
"expected model of type ilayoutedmodelelement, but was " +...Checks of the type
```java">
object model = mvcb.getmodel();
if(!(model instanceof ilayoutedmodelelement)) {
throw new illegalargumentexception(
"expected model of type ilayoutedmodelelement, but was " +
model.getclass().getsimplename() + ".");
}
```
shall be moved to a common base class within the systemfocus kernel.
`mvcbundlepartbase` would be the most common class to place such a
check. this way the class itself does not have to be parameterized while
still avoiding code duplication.
the same base class could be accomodate a generic method for returning
the casted model element:
<code class="java">
protected <t> t getmodelelement(class<t> elementtype)
```
of course calling this method with a wrong parameter leads to class-cast
exceptions, but the expected type is already checked in the constructor.
also, a misuse is limited to derived classes, where a contributor should
know the context.
moreover, the `getname` method of the `contentvisualbase` is currently
returning an empty string, leaving it to its children to implement a
component-specific override. this method is usually identical in all
visuals, except for the class-cast. by using the `getname` method of the
`kerneluiutils` directly in the `componentvisualbase`, this code
duplication could be avoided:
<code class="java
/** {@inheritDoc} */
@Override
protected String getName() {
return KernelUIUtils.getName(getModel());
}
```
*(from redmine: issue id 3877, created on 2019-11-29)*Backloghttps://git.fortiss.org/af3/af3/-/issues/4083AF3 Help is entirely broken under Linux2024-01-11T09:39:12ZAlexander DiewaldAF3 Help is entirely broken under LinuxObserved Behavior
-----------------
The help view just hangs and cannot be closed. AF3 crashes as a whole
and must be force closed after opening the hel This bug was already
present in the 2.17 release and was filed as a nofix.
The iss...Observed Behavior
-----------------
The help view just hangs and cannot be closed. AF3 crashes as a whole
and must be force closed after opening the hel This bug was already
present in the 2.17 release and was filed as a nofix.
The issue has been reported upstream to eclipse and seems related to
JFX: https://bugs.eclipse.org/bugs/show_bug.cgi?id=564911
Proposed Solution
-----------------
Do not use the built-in eclipse mechanism for displaying the help, but a
custom one like for the DSE perspective hel
*(from redmine: issue id 4083, created on 2020-11-04)*AF3 2.25 - Release HackathonTiziano MunaroTiziano Munaro