DescriptionPierre-Charles David
2016-06-14 04:11:27 EDT
The default rules we apply for properties views when no VSM defines anything more specific are currently relatively basic.
They should be improved to be "good enough" for most metamodels, so that users get nice-looking and fully functional property sheets just by installing the appropriate features.
Achieving this may require changes in the core, not just improving the rules model. For example we probably want to use the "EMF Edit integration services" for all display and edition operations, so we may need a way to register a service class for the context of a Property View Description.
We should review the default rules for the references in order that when a reference is declared with container=true, we must not show the reference in the property view.
We should:
* show mandatory feature in bold and optional in normal,
* show deprecated feature in strikethrough,
* disable non changeable and derived features.
Comment 29Pierre-Charles David
2016-10-06 08:16:59 EDT
There are certainly other improvements possible given the very vague wording of this ticket, but for 4.1.0 we'll consider it done. Ideas for further improvements and bugfixes should be tracked with other, individual tickets.
For validating this, there are no precise instructions: try the default rules with various kinds of models and see if the result makes sense, is usable and does not cause bugs.
