Summary: | Web Inspector: Open resource dialog should assume implicit wildcard in the beginning of the query. | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Vsevolod Vlasov <vsevik> | ||||
Component: | Web Inspector (Deprecated) | Assignee: | Vsevolod Vlasov <vsevik> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | apavlov, bweinstein, eustas.bug, joepeck, johnjbarton, keishi, loislo, pfeldman, pmuellr, rik, timothy, webkit.review.bot, yurys | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
Vsevolod Vlasov
2012-09-27 03:16:30 PDT
Created attachment 165966 [details]
Patch
Comment on attachment 165966 [details] Patch Attachment 165966 [details] did not pass mac-ews (mac): Output: http://queues.webkit.org/results/14035778 New failing tests: http/tests/workers/terminate-during-sync-operation.html Committed r129753: <http://trac.webkit.org/changeset/129753> Yes! Implicit wildcards are a great step in the right direction. With implicit wildcards on the ends, we need only take the next small step and add them between letters. Then we can support queries like "QPanel" when the user has Querypoint.js QuerypointPanel.js Panel.js ScriptPanel.js QuerypointModel.js and so on. Once the user types "Q" the list dramatically and quickly shortens to all things Q, in this case almost exclusively Querypoint*. Rather than tediously typing out "uerypointPa" the user need only add "P" or "Pa" and "enter" to open the file they desire. In general the query and the item list become an interactive selector rather than a static drop down with a static rigid command line. In the place of user total recall and typing we support partial recall and just-enough-typing. The query no longer specifies a selection on a long list, but rather it is a hierarchical, divide and conquer selector where each character divides the list into accept and reject piles. The difference in user performance matches the difference between linear list search algorithms and hierarchical search algorithms. We already support camel case matching, so in your example typing QP should be enough. Do I miss something? (In reply to comment #5) > We already support camel case matching, so in your example typing QP should be enough. Do I miss something? Sorry my mistake: I meant 'qp' From the list: Querypoint.js QuerypointPanel.js Panel.js ScriptPanel.js QuerypointModel.js The query "qp" gives 0 entries in the current implementation. Why should "QP" be interpreted as "*Q*P*" but "qp" as "*qp*"? What should I expect for "qP" and "Qp"? |