Bug 391669 - Start Level in Product configuration file - Plug-in Selection dialog
Summary: Start Level in Product configuration file - Plug-in Selection dialog
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: bugday, helpwanted
Depends on:
Blocks:
 
Reported: 2012-10-11 09:49 EDT by Lars Vogel CLA
Modified: 2014-07-03 19:07 EDT (History)
2 users (show)

See Also:


Attachments
Screenshot (75.95 KB, image/png)
2012-10-11 09:49 EDT, Lars Vogel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2012-10-11 09:49:57 EDT
Created attachment 222178 [details]
Screenshot

I noticed that the Plug-in Selection dialog in the product configuration file for setting the start-levels does not support wildcard search. 

Why not use the same dialog as for the Manifest.MF Add Dependency. This one support also wildcards.

Might be nice to get ride of one additional dialog.
Comment 1 Curtis Windatt CLA 2012-10-11 13:26:04 EDT
The issue here is that we aren't adding from a list of IPluginModelBase objects.  Instead we have a list of IProductPlugins or IFeaturePlugin objects.  To fix this we could enhance the plug-in selection dialog to support other objects that have a plug-in id.  Or we could take the minimal performance hit of looking up the plug-in model for the other objects before opening the dialog.

Note that if this change is made, it should also be applied to PluginSection, SplashLocationSection as well as PluginConfigurationSection in the product editor.

If someone is feeling really ambitious, it could also be replaced in ImplicitDependenciesSection and TargetDefinitionContentPage (BundleInfo objects).
Comment 2 Lars Vogel CLA 2014-07-03 19:07:16 EDT
I think current functionality is fine, marking as WONTFIX.