Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve AADL property editing support in graphical editor #1169

Closed
philip-alldredge opened this issue Apr 25, 2018 · 5 comments
Closed

Improve AADL property editing support in graphical editor #1169

philip-alldredge opened this issue Apr 25, 2018 · 5 comments

Comments

@philip-alldredge
Copy link
Collaborator

Issue by philip-alldredge
Thursday Oct 15, 2015 at 15:54 GMT
Originally opened as osate/osate-ge#140


allow the user to assign AADL property values.

Problems assigning properties to flow paths using the graphical editor. Revisit integration with properties view. Ideally support property associations with applies to along any depth of the model.

A way is needed to visualize and edit properties.

Additionally, specialty menus are needed to set common properties. For example: Delayed/Sampled/Immediate connections. Need to allow user to set it at the desired level without being tedious. Other properties should be supported as well. The AADL properties view has grouping of properties.

Look into how the graphical editor support for AADL properties can be improved and be consistent and potentially build on the capabilities provided by the OSATE core.

@philip-alldredge
Copy link
Collaborator Author

Comment by philip-alldredge
Wednesday May 04, 2016 at 16:13 GMT


There is also an additional issue that if the xtext document is not open, the AADL Properties View does not work. Currently the graphical editor does not provide an XtextDocument but rather edits the resource directly unless the AADL editor is open. Look into whether having an XtextDocument is an option. Could also reduce editing code paths.

@philip-alldredge
Copy link
Collaborator Author

Comment by philip-alldredge
Wednesday Feb 28, 2018 at 15:50 GMT


Need a general mechanism to set properties on end-to-end flows and flow implementations. It has also been suggested that it would be nice to have an easy way to set the latency property when creating such flows.

Is there some way to unify how ETEF and Flow Implementations are handled so that they would be exposed to the properties view and/or outline?

@philip-alldredge philip-alldredge changed the title Improve Property Editing Support in Graphical Editor Improve AADL property editing support in graphical editor Jul 24, 2018
@philip-alldredge
Copy link
Collaborator Author

Consider adding multiple selection.

@philip-alldredge
Copy link
Collaborator Author

If support for the text editor's OSATE's AADL Property Values view is not fixed as part of the task, the integration should be completely disabled.

@philip-alldredge
Copy link
Collaborator Author

philip-alldredge commented Sep 17, 2018

@lwrage @joeseibel:
@RyanMcilnay and I have discussed things and we are looking at focusing on updating things so that the OSATE AADL Property Values view works with the graphical editor in the same was it does for the text editor. Multiple-selection and handling the context information of the graphical editor is something we can look at once the basic functionality is complete. Let us know if you have any objections.

@philip-alldredge philip-alldredge added this to the 2.3.6 milestone Sep 21, 2018
@ghost ghost added in progress and removed next labels Oct 16, 2018
@lwrage lwrage modified the milestones: 2.3.6, 2.4 Oct 17, 2018
@lwrage lwrage added review and removed in progress labels Nov 13, 2018
@ghost ghost removed the review label Nov 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants