AF3 issueshttps://git.fortiss.org/af3/af3/-/issues2023-01-26T10:13:10Zhttps://git.fortiss.org/af3/af3/-/issues/3966Channel creation between components2023-01-26T10:13:10ZJohannes EderChannel creation between componentsCreation of channels between components shall be enabled, such that
ports get automatically created if necessary.
Following cases have to be covered:
- Port to Component (new Port is created)
- Component (new Port is created) to Po...Creation of channels between components shall be enabled, such that
ports get automatically created if necessary.
Following cases have to be covered:
- Port to Component (new Port is created)
- Component (new Port is created) to Port
- Component (new Port is created) to Component (new Port is created)
- Port to Context
- new Component+Port is created
- new Port is created on container component
*(from redmine: issue id 3966, created on 2020-03-23)*Backloghttps://git.fortiss.org/af3/af3/-/issues/3965Copy&Paste of components in component/diagram editor2023-01-26T10:12:47ZJohannes EderCopy&Paste of components in component/diagram editorCopy&Paste shall be enabled within component/diagram editor. Currently,
this is only possible via the Model Navigator.
*(from redmine: issue id 3965, created on 2020-03-23)*Copy&Paste shall be enabled within component/diagram editor. Currently,
this is only possible via the Model Navigator.
*(from redmine: issue id 3965, created on 2020-03-23)*Backloghttps://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/3954Model elements view unpredictably collapses and unfolds subtrees2023-03-23T15:46:40ZSimon BarnerModel elements view unpredictably collapses and unfolds subtreesThe model elements view collapses and unfolds subtrees for no good
reason. This might have an annoying effect when modeling larger
architectures.
As far as possible, the bug should be fixed in the underlying
DynamicTreeContentProviderBa...The model elements view collapses and unfolds subtrees for no good
reason. This might have an annoying effect when modeling larger
architectures.
As far as possible, the bug should be fixed in the underlying
DynamicTreeContentProviderBase class. The bug also appears in other tree
views (e.g., data dictionary).
Steps to reproduce (1)
- Create PlatformArchitecture
- Collapse “Hierarchic Architecture” category
- Click on PlatformArchitecture background ->“Hierarchic
Architecture” category is unfolded
Steps to reproduce (2)
- Create PlatformArchitecture
- Search for “Clust” ->only “Hierarchic Architecture ->
Cluster” is shown
- Delete filter
- Now the generic architecture and the RaspberryPi platforms are
collapsed.
*(from redmine: issue id 3954, created on 2020-03-17)*BacklogJohannes EderJohannes Ederhttps://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/3944Define the safety standard by a property of the FileProject2023-01-26T10:49:08ZAlexander DiewaldDefine the safety standard by a property of the FileProjectCurrent status
--------------
There exist (at least) two places where safety standards are defined: At
component architectures and platform architectures (and possibly
requirements). This is a cause for inconsistencies.
Proposed change...Current status
--------------
There exist (at least) two places where safety standards are defined: At
component architectures and platform architectures (and possibly
requirements). This is a cause for inconsistencies.
Proposed change
---------------
Define the safety standard as a property of a FileProject. We can keep
the annotations for component/platform architectures. However, they
shall be changed to access the FileProject’s field. If the value is
changed via one of the annotations, a warning shall indicate the
project-wide change (and possibly required checks).
*(from redmine: issue id 3944, created on 2020-03-13)*Backloghttps://git.fortiss.org/af3/af3/-/issues/3941Allocations editor: Creating a mapping in one tab removes all targets in the ...2023-04-03T07:24:56ZDummy AF3-DevAllocations editor: Creating a mapping in one tab removes all targets in the other tabs.To reproduce:
\- Download the attached model
\- Open the Allocations, “Components → Hardware” editor
\- Check that the “Ports → Transceivers” and “OutputPorts →
Transmitters” tabs have entries for both source and target
\- Go to the ...To reproduce:
\- Download the attached model
\- Open the Allocations, “Components → Hardware” editor
\- Check that the “Ports → Transceivers” and “OutputPorts →
Transmitters” tabs have entries for both source and target
\- Go to the “InputPorts → Receivers” tab and map Input0 to
RaspberryPI.DPadUp
- Check the “Ports → Transceivers” and “OutputPorts → Transmitters” tabs
again
Expected behaviour:
Entries of the “Ports → Transceivers” and “OutputPorts → Transmitters”
tabs should be unchanged.
Obtained behaviour:
Entries for the targets of the “Ports → Transceivers” and “OutputPorts →
Transmitters” tabs are gone.
Notes:
\- Does not affect the “Components → Hardware” tab.
\- Does not affect tabs that haven’t been opened before doing the
mapping.
- Closing and opening the Allocations editor restores all removed
entries
*(from redmine: issue id 3941, created on 2020-03-04)*
* Uploads:
* [Multiplatform_test.af3_23](/uploads/148631c4a6f716190cd90867aea2652d/Multiplatform_test.af3_23)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/3928[safety] The connectors on circle figures (solutions) do not work well2023-01-26T13:36:34ZCarmen Carlan[safety] The connectors on circle figures (solutions) do not work well
*(from redmine: issue id 3928, created on 2020-02-04)*
* Relations:
* relates #3881
*(from redmine: issue id 3928, created on 2020-02-04)*
* Relations:
* relates #3881Backloghttps://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/3895fix an issue with different runtime environments2020-12-05T13:50:03ZDummy AF3-Devfix an issue with different runtime environmentsfix an issue with different runtime environments
*(from redmine: issue id 3895, created on 2019-12-09)*
* Relations:
* parent #3858fix an issue with different runtime environments
*(from redmine: issue id 3895, created on 2019-12-09)*
* Relations:
* parent #3858Backloghttps://git.fortiss.org/af3/af3/-/issues/3894Separate DSR feature from MIRA into "Verification" plugin2020-12-05T13:50:02ZDummy AF3-DevSeparate DSR feature from MIRA into "Verification" pluginSeparate DSR feature from MIRA into “Verification” plugin
*(from redmine: issue id 3894, created on 2019-12-09)*
* Relations:
* relates #3858Separate DSR feature from MIRA into “Verification” plugin
*(from redmine: issue id 3894, created on 2019-12-09)*
* Relations:
* relates #3858Backloghttps://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 #3898Backlog