Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 327258

Summary: Extension elements should have an explicit label property
Product: [Eclipse Project] PDE Reporter: Ralf Ebert <ralf>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: curtis.windatt.public, gunnar, Lars.Vogel, Udo.Walker
Version: 3.7   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Commands without Label in org.eclipse.ui.menus none

Description Ralf Ebert CLA 2010-10-07 13:05:13 EDT 
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.
Comment 1 Ralf Ebert CLA 2010-10-07 13:06:52 EDT 
Created attachment 180442 [details]
Commands without Label in org.eclipse.ui.menus
Comment 2 Curtis Windatt CLA 2010-10-07 15:16:51 EDT 
See also bug 199124, I'm sure I've seen a duplicate for this bug, but I can't find it.
Comment 3 Ralf Ebert CLA 2010-10-08 11:35:14 EDT 
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?
Comment 4 Darin Wright CLA 2010-10-21 10:23:27 EDT 
*** Bug 328318 has been marked as a duplicate of this bug. ***
Comment 5 Gunnar Wagenknecht CLA 2010-12-19 11:34:18 EST 
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.
Comment 6 Lars Vogel CLA 2014-02-06 09:09:29 EST 
Marking as WONTFIX, please open again if you plan to work on it.