Bug 168902

Summary: [ActivityMgmt] Product specific filter for properties pages
Product: [Eclipse Project] Platform Reporter: Randy Giffen <randy_giffen>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: NEW --- QA Contact:
Severity: minor    
Priority: P3 CC: bpasero, Kevin_McGuire, pwebster
Version: 3.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Randy Giffen CLA 2006-12-21 15:47:28 EST 
Build ID: M20060921-0945

Steps To Reproduce:
In a large product (built on a number of underlying products) the number of preference pages can become very large.

We need a way to filter the preference pages to a subset defined by a particular product (with the option to see them all if desired)

1. There are a bunch of root pages that are not helpful e.g. LPEX Editor,

2. And a bunch of pages where only some of their subpages matter. For example under workbench there are a tonne.





More information:
Comment 1 Randy Giffen CLA 2006-12-21 15:50:18 EST 
Adding the following info for my own reference

56743       wbit.ux       open    adamsg         ragiffen    3           25    preferences pages need to be wid ones only
Comment 2 Randy Giffen CLA 2007-02-12 09:47:04 EST 
This is acutally part of a larger problem.
Trying to build a product that hides unwanted functionality in the platform.
Capabilites where designed to help this but fail for 2 reasons:
1) Parts of the UI that do not filter by capabilities
2) Certain base capabilities must be turned on but we still do not
want all their contributions visible in the UI (we would like to 
be able to hide these behind the "show all" checkbox
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:11:02 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.