[mdt-papyrus.dev] Re: Realizing Constraints

[Vincent H <vincent.hemery@xxxxxxxxxxxxxx>]

Hello,

> I thinks that these problems comes from a lack of functionnality in papyrus.
> A value specification can be attached to a constraint. By defaut this is a
> string expresssion.
I also think a feature is lacking in Papyrus.
I think we really need a generic editor to create and edit all kind of 
ValueSpecification.

And I mean all of them, not only a string expression or an OCL 
expression. I think this editor should open as a popup window when 
trying to edit a value expression (as by direct edit on a displaying 
"{...}" label). Then, it should suggest all correct possibilities to 
edit/complete the value specification. (with creation of necessary 
elements on the fly)

Of course, such an editor is not a light task, but an heavy backbone 
task which would benefit all Papyrus diagrams. It needs to be specified, 
and suggested to the community for eventual remarks before implementation.

This should answer at least point d.
> > >  d) The Specification field allows only selection of literals already
> > >  defined; no ability to create a new OCL expression.

An other example of this need :
In Sequence diagram, to edit a TimeConstraint or a DurationConstraint :
By direct editing the label :
 - we are currently able to edit only the name of the constraint (which 
has no sense, but it was the least stupid thing to do without an 
adequate editor).
 - instead, with this ideal feature, we should have the editor opened. 
This editor would allow to edit a TimeInterval (for a TimeConstraint) or 
a DurationInterval (for a DurationConstraint).

Have you ever tried to create by hand a TimeInterval, a DurationInterval 
or even a complex TimeExpression, you would know this is a really 
painful task. We can not expect users to create such complex 
ValueSpecification elements by hand.

Regards,
Vincent.