Bugzilla – Full Text Bug Listing
| Summary: | [CommonNavigator] "Plugin and fragments" Working Set type not supported | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Tod Creasey <Tod_Creasey> | ||||||
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | enhancement | ||||||||
| Priority: | P3 | CC: | caniszczyk, curtis.windatt.public, eclipse, mdelder | ||||||
| Version: | 3.3 | Keywords: | helpwanted | ||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows All | ||||||||
| Whiteboard: | stalebug | ||||||||
| Attachments: |
|
||||||||
|
Description
Tod Creasey
Created attachment 71750 [details]
Before
Created attachment 71751 [details]
After
The "Plugins and fragments" Working set creates model objects that are not supported by any of the Common Navigator extensions shipped in Platform (Resources, Java). Perhaps PDE could consider shipping a Content Extension to show details about the plugins that are selected? Mike, how would this "content extension" work? What does PDE need to do? Mike, ping Hi Chris, This bug was opened due to a defect opened against the Project Explorer where someone tried to create a "Plugins and Fragments" Working Set within the Project Explorer. Currently, the PX doesn't have an extension that can display content (similar to what is displayed in the Plug-ins View). It should be a relatively straightforward process to add an extension that would do this, so I opened this bug for you guys to consider it. It's not a high priority though, more of a nice to have. I would anticipate the requirements for this looking something like: (1) Define an org.eclipse.ui.navigator.navigatorContent extension that declared the PDE's content provider and label provider and triggerpoints/possible children expressions accordingly. (2) Bind the new extension to the Project Explorer (org.eclipse.ui.navigator.viewer/viewer binding) (3) Decide if there's any actions you want to contribute via an Action Provider. If you use object contributions, then those should automatically be picked up. (4) Decide if there's any DND semantics you want to support (e.g. dragging one plugin onto another would maybe create a dependency from one to the other), and if so define a "dropAssistant" under your navigatorContent extension. I'd recommend that by default you _don't_ enable on empty or the workspace, which will ensure you don't contribute content automatically. However if someone creates a working set with plugin model elements, your trigger points should indicate "instanceof SomePluginModelObject" so you'd be invoked to contribute children. Thanks for the ping -- this had fallen off my radar. Doesn't look like there will be time for this in 3.4. Help is always welcome though :) 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. Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release. |