Summary: | [Editor Mgmt] [RCP] A generic way to create IEditorInput instances for an IAdaptable | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Cagatay Kavukcuoglu <cagatayk> |
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | Keywords: | helpwanted |
Version: | 2.0 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Cagatay Kavukcuoglu
2001-11-08 17:02:07 EST
This is an interesting idea. Any implementation for this need to ensure that plugins do not get eagerly loaded and we do not defeat the resource change listeners in Core. Agree that this is a P3 enhancement. I've been thinking of something along these lines. I think we need an open-ended mechanism for mapping from an arbitrary object to an editor input and/or editor id. Using IAdaptable as above is one possibility. An extension point to allow pluggable strategies for this is another. See also bug 74263. It seems like the editor input chosen should be a function of the editor too. We can't limit this to just the default editor case. Reassigning bugs in component areas that are changing ownership. Prakash is now responsible for watching bugs in the [RCP] component area. |