Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368201 - Non-feature label edit parts should have user-readable names
Summary: Non-feature label edit parts should have user-readable names
Status: NEW
Alias: None
Product: GMF-Tooling
Classification: Modeling
Component: Generation / Templates (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Svyatoslav Kovalsky CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-09 17:26 EST by Michael Golubev CLA
Modified: 2012-01-09 17:26 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Golubev CLA 2012-01-09 17:26:00 EST 
Actually for every non-feature based label mapping (that is, for design labels, for labels with externally provided parser and for expression labels) the bridge chooses the EditPart class name based on the FQN of underlying figure. 

The user input (neither in Map nor in Graph models) is not used at all for this naming. 

It leads to the generation of the classes like WrappingLabelEditPart, WrappingLabel2EditPart, WrappingLabel3EditPart and so on. 

Those classes are very difficult to distinguish, e.g during debugging.

=>

It would be much better if the bridge created the user readable class names, based on the user input, e.g, on the names of the DiagramLabel's in the grpah model