Bug 39636 - [About] plug-in details should show more information
Summary: [About] plug-in details should show more information
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2003-07-04 08:22 EDT by Philipe Mulet CLA
Modified: 2019-09-06 16:09 EDT (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 Philipe Mulet CLA 2003-07-04 08:22:27 EDT 
Build 20030107

When browsing plug-in details, and asking more info on a given plugin, the 
about.html is opened, which contains very little additional value in general.

The about.html should probably be a little more descriptive, with links to 
relevant ISV documentation or build notes.

Also the table view should also offer a tree view so as to quickly identify 
groups of plugins (org.eclipse.*).

Last, when asking more details on a given plugin, it could open a PDE editor on 
plugin.xml file in read-only mode, which would allow to browse plugin 
contributions etc...
Comment 1 Philipe Mulet CLA 2003-07-09 10:19:31 EDT 
Build number was actually 20030703
Comment 2 Nick Edgar CLA 2006-03-15 11:56:07 EST 
Reassigning bugs in component areas that are changing ownership.
Comment 3 Boris Bokowski CLA 2007-01-02 11:10:00 EST 
Reassigning bugs to reflect changes in ownership.
Comment 4 Susan McCourt CLA 2009-06-25 15:18:55 EDT 
reassigning remaining [About] bugs according to 2009 platform-ui triage guidelines
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:09:23 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.