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
Comments
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. |
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? |
Consider adding multiple selection. |
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. |
@lwrage @joeseibel: |
Thursday Oct 15, 2015 at 15:54 GMT
Originally opened as osate/osate-ge#140
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.
The text was updated successfully, but these errors were encountered: