@TiddlyTweeter wrote:
>
> I agree that a "combinatorial" approach is optimal. Filters may be able to
> do it. But filter syntax can get complex.
>
>
A really easy filter syntax with full power under the hood:
- mes
*default* search field behavior: every tiddler with match in fields:
title, text or tag
- 🎯mes
direct hit at field: every tiddler with match for "mes" in field title
(shorthand)
- 📌title:mes
pinned field
every tiddler with match for "mes" in field title (long notation)
- 🚫mes
not operator
every tiddler not match "mes" in title (shorthand)
- 📌title🚫mes
every tiddler not match "mes" in title (long notation)
- 📌title:mes📌tag:con
every tiddler with match for "mes" in title *and* "con" in tag
run [...] <=> logical and <=> default for several fields
- 📌title/mes/i📌tag:con
*RegEx* object
- 🔋🎯m*s
little power of battery
SQL wild card search MS Access dialect
- 🔌🎯m%s
big power of power grid
SQL wild card search MS SQL dialect
- mes📍📌tag:con
logical OR operator
"mes" match in title *OR* "con" match in tag (shorthand)
- 📌title🚫mes📍📌tag:con
"mes" not match in title *OR* "con" match in tag (long notation)
I think the principle is clear.
You need emojis for every operator.
Or is there a graphic designer in the forum who could design TiddlyWiki
search icons?
And tomorrow I will post my ideas on how to use this with a super simple
designed "search"-input field, so that Advanced Search is only needed in
exceptional cases.
(But technically/internally the "search"-input field is a kind of remote
control for the Advanced Search tiddler.
Regards
Cd.K
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/8e48398f-75b7-48ec-b9ca-cc065ccef253%40googlegroups.com.
