Bug 15281

Comment 1 Peter Manahan 2002-05-05 11:01:36 EDT

The Feature XML editor. Content pane. Button "New" to add plugins and fragments 
to the feature has 2 problems
1) It isn't honoring the "use identifier in editor's and dialogs" preference 
which makes it really difficult to decide which plugins are loaded (i.e can't 
tell between com.ibm and org.eclipse  in my case)
2) There doesn't seem to be a way to add plugins and fragments that aren't in 
the workspace. This forces a load of all the plugins and fragments in the 
target platform as binary projects.h

Comment 2 Dejan Glozic 2002-05-08 19:38:00 EDT

Problem 1) should be fixed.

Problem 2) is not really a problem. The reason you want to use PDE editor as 
opposed to a stock XML editor is to get the extra value that comes from PDE 
knowing the problem domain. Consequently, PDE can only compute required plug-
in, download and install sizes, correct versions and IDs etc. if the plug-in 
reference can be resolved. If not, PDE still allows you to do it manually, but 
will not offer any help beyond source page, because allowing you to enter 
random text for plug-in ID and version is no value add IMHO.

BTW, this behavour is consistent with plug-in manifest editor, where you can 
only add dependency if the referenced plug-in is present in the workspace or 
the target platform. Otherwise, you will have to switch to the source page to
type the import entry.

Fixing 1), passing on 2).