Show placeholder for expected signature for attributes and operations

[Matthias Schoettle]

Often new users don't know how to type in the signature of attributes or operations. It would be good to show a placeholder text (similar to when a new class is created) that shows the expected signature.

For operations it might be necessary to look for an alternative, since the signature description could be quite long, although the user will type in a signature that could be just as long (approx.).

[Matthias Schoettle]

Would be nice to have for the demo :)

[Laura Martellotto]

References issue #75 : Added placeholders for attributes and operations and let them when the caret is enabled

→ <<cset c8633b47f533>>

[Laura Martellotto]

In order to inform the user on what he is supposed to write, I think it is more friendly to let the placeholders when the field is empty AND even if the caret is enabled. Placeholders disappear when the field is not empty. Tell me if it's no good ! Maybe the placeholder for operation is too long ? And maybe can I add placeholders for enum too, when user has to add values ?

[Matthias Schoettle]

In order to inform the user on what he is supposed to write, I think it is more friendly to let the placeholders when the field is empty AND even if the caret is enabled. Placeholders disappear when the field is not empty. Tell me if it's no good !

That's a good idea.

And maybe can I add placeholders for enum too, when user has to add values ?

That would be great. Maybe even for new parameters. For enums, somehow we should show the user that one or several literals can be added. Maybe "<literal>[, <literal>]" or something like that? Or is that too confusing?

[Laura Martellotto]

References issue #75 : Added placeholders for enums and new parameters.

I agree with you, I think it is more understandable ! Moreover, it is quite magical for new parameters in operations : the placeholder allows to fix the bug of the caret which was in wrong place.

→ <<cset 734005b10aa5>>