Bug 97940

Summary:	[WorkbenchLauncher] "Loading Plugins" startup dialog should use presentation names
Product:	[Eclipse Project] Platform	Reporter:	Adam Kiezun <akiezun>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	b.muskalla, bpasero, hudsonr, jeffmcaffer, michaelvanmeekeren, n.a.edgar, pascal, prakash
Version:	3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	154088

Description Adam Kiezun

2005-06-01 14:17:48 EDT

3.1RC1
currently it uses the IDs, like 'org.eclipse.ltf.refactoring' etc.
This is too low level. It should use the plugins' presentation names, like "CVS
Team Provider UI" etc

Comment 1 Boris Bokowski

2005-06-01 15:05:37 EDT

Without Core caching these names, it is a performance problem to show the nice 
names instead of the IDs.  The manifest files and the translation files for all 
activated plug-ins would have to be read on startup.

Setting target milestone to 3.2.

Comment 2 Boris Bokowski

2005-07-18 10:16:50 EDT

*** Bug 104049 has been marked as a duplicate of this bug. ***

Comment 3 Boris Bokowski

2005-07-18 10:18:48 EDT

[this is a copy of Randy's suggestions from bug 109049:]

Instead of plug-in IDs, it would be more interesting for the user to see [NLed]
names that mean something.  Such as "Java Development Tooling". Another
possibility is to display an Image for the plug-in, feature, or maybe just
provider, perhaps as accumulating icons similar to the way Mac OS boots.

Comment 4 Boris Bokowski

2006-04-12 14:30:00 EDT

Not for 3.2

Comment 5 Boris Bokowski

2009-11-26 16:33:28 EST

Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.

Comment 6 Eclipse Webmaster

2019-09-06 16:07:47 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.