Bug 358077

Comment 1 Camille Letavernier 2011-09-19 05:34:23 EDT

Profile :

An imported metaclass in a UML profile should have its own property view (With the Name & QName properties) ; not the standard UML Class property view

The isRequired property for an Extension should be editable from the property view (This is a derived property)

We should see the MetaclassReference and MetamodelReference properties in the profile property view

Comment 2 Camille Letavernier 2011-09-19 05:45:39 EDT

(In reply to comment #1)
> Profile :
> 
> An imported metaclass in a UML profile should have its own property view (With
> the Name & QName properties) ; not the standard UML Class property view
> 
> The isRequired property for an Extension should be editable from the property
> view (This is a derived property)
> 
> We should see the MetaclassReference and MetamodelReference properties in the
> profile property view

Done in r5498 (Branch 0.8.X)
Merged to the trunk in r5500

Comment 3 Camille Letavernier 2011-09-19 08:39:46 EDT

The Label Provider used in the property view for the following non-named element has been improved :

- Image
- Element import
- Package import

Comment 4 Camille Letavernier 2011-09-19 08:40:08 EDT

(In reply to comment #3)
> The Label Provider used in the property view for the following non-named element
> has been improved :
> 
> - Image
> - Element import
> - Package import

Done in r5505 (Branch 0.8.X)
Merged to the trunk in r5507

Comment 5 Camille Letavernier 2011-09-20 10:18:12 EDT

The Image label has been improved :

- An EAnnotation has been added to set a "name" to the Image (Which is not a NamedElement)
- The name can be edited through the property view
- If the name is set, it will appear in the Image label

Done in r5517 (Branch 0.8.X)
Merged to the trunk in r5518

Comment 6 Camille Letavernier 2011-09-21 08:11:14 EDT

Removed the "package merge" property from the profile property view

Done in r5526 (Branch 0.8.X)
Merged to the trunk in r5527

Comment 7 Camille Letavernier 2011-09-22 05:04:42 EDT

The extensionEnd property view contains a few mistakes :

- The Aggregation property is an Enum, but the widget is a Boolean editor
- The Aggregation property should always be set to "composite"
- The Multiplicity can only be either 1 or 0..1

Fixed in r5538 (Branch 0.8.X)
Merged to the trunk in r5539

Comment 8 Camille Letavernier 2011-11-25 09:28:40 EST

Changed the labels of the "Add" and "Delete" button for Stereotype application :

- Apply stereotype
- Remove stereotype

Comment 9 Camille Letavernier 2011-11-25 09:30:24 EST

> Changed the labels of the "Add" and "Delete" button for Stereotype application :
>
> - Apply stereotype
> - Remove stereotype

Done in r6299 on the branch (0.8.X)

Comment 10 Camille Letavernier 2011-12-14 05:56:39 EST

Fixed some UML Label Providers

r6453 (Branch 0.8.X)
r6463 (Trunk)

Comment 11 Camille Letavernier 2013-01-30 05:00:48 EST

r9917 on the trunk (0.10.X): I've added the ownedAttribute editor to a few Classifiers (Interface, Class, DataType, AssociationClass, ...)

Comment 12 Camille Letavernier 2013-01-31 10:48:46 EST

r9957: The properties view of the Image has been extended to allow usage of file references.

It is now possible to specify URIs to the image (platform:/plugin/<plugin.id>/path/to/image, platform:/resource/<project.name>/path/to/image)

Comment 13 Camille Letavernier 2014-03-03 05:37:00 EST

36e7c9e on master:

- Add a properties view for SignalEvent (Which used to reuse the generic Event properties view).

Especially, the SignalEvent#signal property was missing

Comment 14 Dan George 2014-03-03 12:16:29 EST

The +signal property of SignalEvent is missing (See Events, Abstract Syntax).

This property is important for implementing an Executable UML model compiler. I need to relate State entry action->Transition->trigger->SignalEvent->Signal so that I can implement a parameter passing mechanism. Specification of the trace to the Signal Attributes is also necessary to validate the model. In Executable UML, all incoming transitions must have triggers the resolve to Signals having a common set of Attributes.

I'm really excited to get going with my Eclipse-based Executable UML model compiler. Is there any way I can help add the support?

Comment 15 Camille Letavernier 2014-03-03 12:21:06 EST

Reporting the missing entries is sufficient, thanks :)

Actually, I've fixed that already this morning (See Comment 13)

Comment 16 Camille Letavernier 2014-06-30 05:30:40 EDT

Commit af80d74 on master:

- Add Port#type for multi selection
- Add Trigger#port for single selection
- Fix the multiplicity of Trigger#port in the UML properties view definition

Comment 17 Camille Letavernier 2014-09-08 10:45:27 EDT

Commit 272a5a1 on master:

- Add Activity#ownedParameters and remove Activity#useCase (For single Selection of an Activity)