Community
Participate
Working Groups
Currently PDE shows the first string attribute as label text for the element nodes in the extension editor. For some org.eclipse.ui extension points, this choice is unfortunate. For example, when adding commands using org.eclipse.ui.menus, the label attribute is shown. Most of the time, you don't specify a label because the command already gets a label from the command definition. This yields not very helpful node labels in the tree (see attached screenshot). Manually entering an explicit label would overwrite the internationalized labels from the original command definition, so this is not really a solution. imho the extension schema author should be able to pick the attribute(s) which should be used for the tree nodes in the extension editor.
Created attachment 180442 [details] Commands without Label in org.eclipse.ui.menus
See also bug 199124, I'm sure I've seen a duplicate for this bug, but I can't find it.
Too bad that a "Label property" configuration for elements already existed and was removed in 2007 with Bug 196882 Personally I can't agree on the argumentation back then, sacrificing usability of the extension editor for simplification of the schema metadata. Are there other ideas how this problem could be solved / are there any objections to bringing back the explicit configuration as optional attribute?
*** Bug 328318 has been marked as a duplicate of this bug. ***
Thank god it hasn't been removed completely. However, having to hack XML to get i back is just poor usability. +1 for bringing it back in the Schema editor.
Marking as WONTFIX, please open again if you plan to work on it.
