Community
Participate
Working Groups
I had to copy org.eclipse.ui.internal.misc.StringMatcher in p2 to provide wild card auto-complete in a wizard. I noticed copies of the class in JDT, PDE, IDE, etc.... We should look at making this API, probably in JFace. Then it could be used by the JFace field assist auto complete, as well as the dialogs.
I count at least 8 places that it's used. Since we are past API freeze, we would have to get PMC approval to get this in.
I was assuming 3.6, no rush...
I would prefer 3.5 and the ability to reduce code is a good thing (tm). What do you think?
Created attachment 129397 [details] org.eclipse.jface.patch A first stab at a patch based on the JDT implementation. There's some documentation to do still...
thanks for the patch. We have so many of these situations, I don't see treating StringMatcher as a special case and pushing this into 3.5 past API freeze. To add any value, clients would have to switch to it, and then if there are behavior differences/bugs I've got RC bugs I don't need...
*** Bug 280514 has been marked as a duplicate of this bug. ***
Added my self to CC. Isn't there a more silent way of this?
(In reply to comment #7) > Added my self to CC. > Isn't there a more silent way of this? Just use the 'Add CC:' field in the top right corner and type your email address there.
This should be marked as duplicate of bug 2382 and bug 2382 be reopened. Also note that UI is probably the wrong layer to add this API as some core plug-ins also maintain a copy of StringMatcher.
A four digit bug number. Wow. Marking duplicate *** This bug has been marked as a duplicate of bug 2382 ***