After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 619061 - add search history and auto-completion
add search history and auto-completion
Status: RESOLVED FIXED
Product: tracker
Classification: Core
Component: Search Tool
git master
Other Linux
: Normal normal
: ---
Assigned To: tracker-search-tool
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2010-05-19 07:52 UTC by Tshepang Lekhonkhobe
Modified: 2010-05-21 07:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
history+autocompletion (8.66 KB, patch)
2010-05-19 07:52 UTC, Tshepang Lekhonkhobe
needs-work Details | Review
history+autocompletion (8.78 KB, patch)
2010-05-20 07:34 UTC, Tshepang Lekhonkhobe
committed Details | Review

Description Tshepang Lekhonkhobe 2010-05-19 07:52:47 UTC
Created attachment 161411 [details] [review]
history+autocompletion

This partly implements the request from https://bugzilla.gnome.org/show_bug.cgi?id=581343, that's why it's done as a separate report.
Comment 1 Martyn Russell 2010-05-19 08:44:35 UTC
Comment on attachment 161411 [details] [review]
history+autocompletion

The patch looks good, but in testing I notice that after the 4th character in a lot of cases, it does the search even if I am still typing and have not experienced the 500ms timeout. This means that for "martyn", I see history of "marty" and "martyn".

I think this needs to be fixed first, but then we can commit this.
Comment 2 Tshepang Lekhonkhobe 2010-05-20 07:34:58 UTC
Created attachment 161521 [details] [review]
history+autocompletion

here fixing the issue
Comment 3 Martyn Russell 2010-05-20 08:28:09 UTC
Comment on attachment 161521 [details] [review]
history+autocompletion

Looks good to me, thanks for the patch!
Comment 4 Martyn Russell 2010-05-20 08:28:48 UTC
For the future, could you make sure you commit message includes the bug number so we don't forget it for releases, thanks.

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 5 Jamie McCracken 2010-05-20 14:52:48 UTC
It was ,ostly ok but...

patch was not utf-8 compatible

string.len should not be used as its the byte length - use utf8 length

Also min length should use preference and also if its CJK entered be ignored (cause words in CJK are typically 1 character long)
Comment 6 Tshepang Lekhonkhobe 2010-05-21 07:29:13 UTC
1. Looking at vala GLib API, string.len is an 'alias' for g_utf8_strlen.
2. "min length should use preference" should be filed as a separate bug
3. I don't understand the note regarding CJK.