| Age | Commit message (Collapse) | Author |
|---|
|
On that page, we have regular expressions (which are not new-user
friendly) and an example (which is new-user friendly). So the example
should come before the regular expressions.
|
|
This commit contains the bulk og the material changes for which the
previous commits established the basis.
1) Add a general framework for detecting query prefixes in search URLs,
adding them to query sent to the completion engine, and stripping them
from the resulting suggestions. This allows the user to have a
search engine...
j: http://www.google.com/search?q=javascript+%s Javascript
and have the prefix "javascript" included (automatically) in queries
sent to completion engines, which results in substantially better
suggestions.
2) Re-work completion for Google Maps in a simpler form.
|
|
The original completion-engine interface was based on three functions.
With some experience, it seems there is a pattern involving explicit
regular expressions which is used by all actual engine implementations.
This is a refactoring to make those regular expressions explicit (and
required), and is a first step towards adding additional fucntionality.
This also simplifies the completion cache key (use JSON instead of some
weird hash).
|
|
|
|
Instead of just giving an example search URL, we can give the actual
declaration (which the user can copy, paste and tweak).
|
|
This allows the user to copy and paste search URLs from this page into
the options page.
|
|
|
|
|
|
|
|
|
