summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorArun Isaac <arunisaac@systemreboot.net>2022-07-11 17:20:33 +0530
committerArun Isaac <arunisaac@systemreboot.net>2022-07-11 17:20:33 +0530
commitb6aaf3ba293c9cfc52ba1ff9ae11a266720a7635 (patch)
tree3409cfc9298283ebfc45227d8fa1eb9dd8cf7f2d
parente0ed1afc72619baef3597195bf73ededa35d0f29 (diff)
downloadtissue-b6aaf3ba293c9cfc52ba1ff9ae11a266720a7635.tar.gz
tissue-b6aaf3ba293c9cfc52ba1ff9ae11a266720a7635.tar.lz
tissue-b6aaf3ba293c9cfc52ba1ff9ae11a266720a7635.zip
issues: Implement incremental search.
* issues/incremental-search.gmi: New file.
-rw-r--r--issues/incremental-search.gmi13
1 files changed, 13 insertions, 0 deletions
diff --git a/issues/incremental-search.gmi b/issues/incremental-search.gmi
new file mode 100644
index 0000000..558eeb5
--- /dev/null
+++ b/issues/incremental-search.gmi
@@ -0,0 +1,13 @@
+# Incremental search
+
+* tags: enhancement, web ui
+
+We could implement "incremental search" in the web UI. Incremental search is a real-time search feature in which results matching a query are immediately rendered on the page. This is like how Helm and similar work on Emacs.
+=> https://en.wikipedia.org/wiki/Incremental_search Incremental search on Wikipedia
+
+According to the above Wikipedia article, Google implemented incremental search under the name "Google Instant", but later discontinued the service. I wonder why.
+
+For incremental search with Xapian, special considerations with the query parser apply.
+=> https://xapian.org/docs/queryparser.html#partially-entered-query-matching Considerations for partially entered query matching with Xapian's query parser
+
+Incremental search would incur a significantly higher bandwidth cost than regular delimited search. It should be strictly optional. The page should fall back to delimited search when it is disabled (say, when javascript is disabled).