Bug 97940 - [WorkbenchLauncher] "Loading Plugins" startup dialog should use presentation names
Summary: [WorkbenchLauncher] "Loading Plugins" startup dialog should use presentation ...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 104049 (view as bug list)
Depends on:
Blocks: 154088
  Show dependency tree
 
Reported: 2005-06-01 14:17 EDT by Adam Kiezun CLA
Modified: 2019-09-06 16:07 EDT (History)
8 users (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 Adam Kiezun CLA 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 CLA 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 CLA 2005-07-18 10:16:50 EDT 
*** Bug 104049 has been marked as a duplicate of this bug. ***
Comment 3 Boris Bokowski CLA 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 CLA 2006-04-12 14:30:00 EDT 
Not for 3.2
Comment 5 Boris Bokowski CLA 2009-11-26 16:33:28 EST 
Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.
Comment 6 Eclipse Webmaster CLA 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.