Summary: | [ActivityMgmt] Component capabilities and overrides | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Tim deBoer <deboer> |
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | david_williams, pwebster |
Version: | 3.4 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Tim deBoer
2007-11-20 10:31:52 EST
You can do most of what you want to do already. You can define the capability separate of the category and enablement state - they are all done by separate elements. Combining two capabilities isn't easily achieved at the moment but I'd entertain ideas of how that might work. Keep in mind that time for new API in 3.4 is rapidly dwindling and we don't currently have any time allocated for further work on capabilities. A concise explanation of what you'd like this to look like would be helpful. Ok, sorry for the delay. What I'm asking is this: 1. Move capabilities for the Eclipse platform from source features into the regular features so that they can be reused and are part of the 'install' of the base platform. Other projects would hopefully take this lead or I'll follow up with other bugs. 2. Whether this release or not, some adopter will eventually disagree with these 'default' capabilities. We either need to make a design decision that capabilities are now component based and everyone needs to live with these, or start allowing capabilities to be overridden. In the simplest case it would just be an extension point to remove a capability or override it with another. 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. |