Description Nicolas Rouquette 2007-02-08 18:30:45 EST

Build ID: I20061214-1445

Steps To Reproduce:
1. Eclipse 3.3M4 + UML2.1M4
2. File | New => Examples>UML Profile Diagram
3. In UML Profile Diagram, create a stereotype
   with an attribute property.
4. Save.

case1: ProfileD with properties view

1. Window | Show View | Other... => Properties
2. ProfileD => select the stereotype property
3. Properties view => scroll to the "Type" entry.
4. Click on the "Value" column of the "Type" property.
5. THe drop-down list shows entries like this:

<<eDataType>> <Primitive Type> String
<<eDataType>> <Primitive Type> String
...

case 2: org.eclipse.uml2.uml.editor with property view.

1. open the *.uml file of the *.umlprofile_diagram above.
1. Window | Show View | Other... => Properties
2. Scroll to the "Type" property of the class attribute.
3. Click on the "Value" field of that property.
The drop-down list includes these entries:
ecore::EENum
Ecore::EENum
ecore::EString
ecore::String
uml::String
UMLPrimitiveTypes::String

Suggestions:

1) A "pathmap/prefix" view listing all of the namespaces.

This would help disambiguate the possible confusion
between ecore::EString vs. Ecore::EString for example.

2) A tree-like ui widget for editing 
the values available for certain property entries used in both EMF, UML2 and UML2Tools using the ExtendedPropertySheetPage of org.eclipse.emf.edit.ui.view

For example, define alternative extensions of PropertySheetSorter from org.eclipse.ui.views.properties
or perhaps of the ExtendedPropertySheetPage to 
present the available options in terms of a tree
instead of a linear list.

One extension might organize the tree by grouping
entries by common namespace prefix / pathmap alias.
Another extension might organize the tree by grouping
entries according to the last "name" and if multiple
namespaces have distinct entries with the same name,
then the children nodes of that name would show the different namespaces/prefixes/pathmap aliases where they come from.

More information:
http://www.eclipse.org/newsportal/article.php?id=151&group=eclipse.modeling.mdt.uml2#151