Summary: | [Editor Mgmt] DCR: Mutliple editor contributors (1GCUHNR) | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Nick Edgar <n.a.edgar> |
Component: | UI | Assignee: | Kevin Haaland <Kevin_Haaland> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 | Keywords: | investigate |
Version: | 2.0 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Nick Edgar
2001-10-10 22:22:51 EDT
PRODUCT VERSION: RH requests: I have a suggestion for a future release of the Workbench regarding Editor contributors. Rather than having the workbench define that there will be one instance of a contributor per Editor type per Workbench window, let the Editor itself determine how many instances there should be. This would be analogous to asking the Editor for its ContentOutline page, which is what currently happens, versus defining the ContentOutline page in XML. Some editors could return a reused instance of a contributor, whether there is just one per workbench Page or one for all of the workbench would depend on the Editor. Some editors might want a new contributor instance for each instance of an editor. By using getAdapter(IActionBarContributor), the Editor could decide. Randy Hudson P.S. This solution could even be phased in without affecting client code. Since unknowning Editors will return null for getAdapter(), the workbench could revert to the current style of looking for a plugin extension in plugin.xml This is an interesting idea Reopen for investigation Defer |