Community
Participate
Working Groups
That would be groovy if the "Open Plug-in Artifact dialog" could display (and allow searching through) the "id" attribute of an extension when it exists. Clients of o.e.c.r.applications, o.e.c.r.products etc. use it and I'd find it very useful to be able to find the "antRunner" application, for example, typing just a few letters... But we must wait 3.5, right?..
I think the matched text should appear in the label of every matched entry. In the screenshot from bug 230248 comment 6, it looks strange that "*participa" matches "org.eclipse.core.filebuffers.documentSetup - ...". You'd probably have to introduce a new entry kind "ID" whose name is the id and whose post-qualification is the extension point name and the contributing plug-in.
(In reply to comment #1) > I think the matched text should appear in the label of every matched entry. In > the screenshot from bug 230248 comment 6, it looks strange that "*participa" > matches "org.eclipse.core.filebuffers.documentSetup - ...". I of course did that, but I removed it just before making the screenshot... I just forgot to remove the "matching" code! :) In my former label provider, I displayed the ID between brackets (ie. "org.eclipse.core.runtime.applications [org.eclipse.ant.core.AntRunner] ......"). It will probably be even prettier when we'll use owner draw labels (see bug 219271) > You'd probably have to introduce a new entry kind "ID" whose name is the id and > whose post-qualification is the extension point name and the contributing > plug-in. Why not..! Doing that will also allow to match inner IDs (like IDs of views, perspectvies, etc.), and not only extension IDs!
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.
