Community
Participate
Working Groups
0.3 M2 We are currently escaping all special characters in the search box, including * and ?. I think we should be consistent with Eclipse search and support * and ? wildcards by default, allowing them to be escaped via \* and \?.
Libing, if I change this on the server we would need to be consistent in the client-side post-processing. Does this change make sense to you?
If we do this, we should explain that wildcards are supported using a tooltip on the search text field.
(In reply to comment #1) > Libing, if I change this on the server we would need to be consistent in the > client-side post-processing. Does this change make sense to you? Currently, client uses simplest string search(string.indexOf) for inside-file search. For wild card search, I have to change that by using reg ex.
It's something we could move to 0.4 if it is complicated. On the server it already works, it just depends on whether you escape the wildcard character on the client before sending the query.
(In reply to comment #4) > It's something we could move to 0.4 if it is complicated. On the server it > already works, it just depends on whether you escape the wildcard character on > the client before sending the query. I just gave it a quick try on something like "text*view", server did respond something but client gave 0 match. I think for 0.3 the bottom line is to escape those * and ?.
fixed with 5d32838a0c5800ddd8e99ea351f2e41299e1e1c1.
There is a tool tip now on the search box: "Type a keyword or wild card to search", and place holder :"Search". If any one has good idea about indicating wild card search please comment.
(In reply to comment #7) > There is a tool tip now on the search box: "Type a keyword or wild card to > search", and place holder :"Search". > If any one has good idea about indicating wild card search please comment. I think this comment belongs in another bug (where search scope text was added to the search box) but I can't find that bug (sorry). I think it's confusing to have the search scope showing in the box, especially the one that says "Search root". I suggest we always just have "Search" in the box. And then the tooltip can give the scope. I also suggest we simplify the tooltip to say "Search in <scope>" and then the results page can talk about wildcards, etc. I think most people assume they can type wildcards and then if they want to know how to use search they go to the advanced page. For something in the header, I think the text and tooltips need to be as simple/terse as possible to reduce noise.
Created attachment 207047 [details] affordance text in Windows explorer search box
(In reply to comment #8) > I think it's confusing to have the search scope showing in the box, especially > the one that says "Search root". > > I suggest we always just have "Search" in the box. > And then the tooltip can give the scope. > I also suggest we simplify the tooltip to say > "Search in <scope>" I agree about the root case. Maybe for the root we just say "Search". But for other folders I think it is a useful affordance to tell the user that the search they are performing here is scoped. This isn't immediately obvious as often a search bar at the top is a global search unless otherwise configured (think web browsers). I remember noticing this recently in Windows 7 (see attachment) and without it I would have assumed the search bar was global. If the user doesn't realize their search was scoped they might be frustrated by not finding the results they expect.
Maybe making the search box wider would help. The windows one has never seemed funny looking to me, while this one does. (Or maybe I'm just used to it being empty).
(In reply to comment #11) > Maybe making the search box wider would help. The windows one has never seemed > funny looking to me, while this one does. (Or maybe I'm just used to it being > empty). Bug 363740 is the original one addressing tool tip and place holder. I am adding bug 363740 comment 3 there.
