Summary: | Extension Point enhancement | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] PDE | Reporter: | Benjamin Muskalla <b.muskalla> | ||||
Component: | UI | Assignee: | Benjamin Muskalla <b.muskalla> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P3 | CC: | pombredanne, wassim.melhem | ||||
Version: | 3.2 | Keywords: | contributed | ||||
Target Milestone: | 3.3 M1 | ||||||
Hardware: | PC | ||||||
OS: | Linux-GTK | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Benjamin Muskalla
2006-06-26 13:08:44 EDT
This is a good idea. We already do something similar when doing an extension point search on the Search > Search... > Plug-ins search page. Chris, if the filter string does not contain a dot or ? or *, we should match for *.filter*, eg. if the user enters 'per', we should match on '*.per*' If the filter text entered by the user contains *, ? or a dot, then it's business as usual. Created attachment 46356 [details]
Extends the Filter to find specific extensions faster
Please be patiend, it's my first patch :-)
Hope this will fulfill the enhancement
Patch released. Thanks Ben. You forgot to run Source > Externalize Strings... on the code though ;) |