Bug 448384 - [TextEditors] Embedded editors must be improved
Summary: [TextEditors] Embedded editors must be improved
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Others (show other bugs)
Version: 1.1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: M3   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-22 10:35 EDT by Camille Letavernier CLA
Modified: 2017-09-08 09:52 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Camille Letavernier CLA 2014-10-22 10:35:39 EDT
Currently, XText editors have a strict grammar, where almost all elements are required (e.g. for a property: visibility, type, multiplicity are required). Most elements should be optional: if it is not specified, then it should remain unchanged. For example, in a Property Editor, typing "p3 [*]" should only change the Name and Multiplicity, and leave the visibility and type unchanged.

The allowed default values should be improved as well, for Property and Port editors: currently, they only support LiteralString default values. At least all Literals should be supported (InstanceValues or Expressions being more complicated and out of the scope of a lightweight editor)
Comment 1 Camille Letavernier CLA 2014-10-22 11:07:02 EDT
The following improvements have been pushed to master:

- Make most grammar elements optional in the Property grammar (Everything but Derived and Name)
- Make most grammar elements optional in the Port grammar (Everything but Derived, Conjugated and Name)
- Improve formatting of the initial text when editing a Port or a Property
- Add support for all Literals in Default Value (For Port and Property). The keywords "null" (LiteralNull) and "none" (No default value) have been added