Could we have a fusion between the list widget with conditional syntax?

#1

I like the options the conditional shortcut syntax offers in an elegant way, but in many cases, I would the <currentTiddler> variable within. This is why I often end up stacking lists in emptyMessages. Could we have the best of both worlds in one widget?

I also would like to have something for the scenario where the results of a first list should excluded from the second list.
Like

  1. searchresults where string is in title, alias
  2. searchresults where string is in caption - results of 1
  3. searchresults where string is in tags -(1+2)
  4. searchresults where string is in text -(1+2+3)
#2

I am not sure I follow but;

I know we have customarily also used the list widget for conditional branching. If in this case it often has one or no, or one of two outcomes (thus emptyMessage). With the advent of %if else we can have more complex structured and optimal decision trees however lets not forget the $list widgets core functionality which is to generate a list to process iteratively (or recursivly).

Of course all of this gets more complex when some fairly advanced and cumulative logic in filters and functions including filters/functions that are themselves conditional, recursive and/or iterative.

For this reason now I tend to separate the list function from the conditional function when using List, and use %if else when it is mostly conditional. In many cases nesting if and listing in each other or both depending on the problem.

#3

The documentation for Conditional Shortcut Syntax says:

Within an “if” or “elseif” clause, the variable condition contains the value of the first result of evaluating the filter condition.

Thus, within a particular “if” or “elseif” clause, you can set <<currentTiddler>> by writing:

<$tiddler tiddler=<<condition>>>
...
</$tiddler>

or, if you prefer:

<$let currentTiddler=<<condition>>>
...
</$let>

-e

1 Like
#4

Thank you @EricShulman, I overread this!
This is already very helpful and would be worth also an example in the documentation. The TLDR; way is to look right there - I am afraid.

But my searchresult-riddle is still unsolved.
My solution is not great yet and adding more options gets really tedious if you want a short resultlist where the same tiddler does not appear 4 times…

<$list filter="[!is[system]search:title{$(searchTiddler)$}sort[title]limit[1]]" >
//<small>im Titel: <br></small>//</$list>
<$list filter="[!is[system]search:title{$(searchTiddler)$}sort[title]limit[250]]" template="$:/plugins/JJ/multimenu/AliasTemplate"/>
<$list filter="[!is[system]search:alias{$(searchTiddler)$}sort[title]limit[1]]-[!is[system]search:title{$(searchTiddler)$}sort[title]]">//<small>Alias-Titel</small>//</$list><$list filter="[!is[system]search:alias{$(searchTiddler)$}sort[title]limit[250]]-[!is[system]search:title{$(searchTiddler)$}sort[title]limit[250]]"template="$:/plugins/JJ/multimenu/AliasTemplate"/>
<$list filter="[!is[system]search{$(searchTiddler)$}sort[title]limit[1]]-[!is[system]search:alias{$(searchTiddler)$}sort[title]limit[1]]-[!is[system]search:title{$(searchTiddler)$}sort[title]limit[1]]">
//<small>im Text:</small>//
</$list>
<$list filter="[!is[system]search{$(searchTiddler)$}sort[title]limit[250]]-[!is[system]search:alias{$(searchTiddler)$}sort[title]limit[250]]-[!is[system]search:title{$(searchTiddler)$}sort[title]limit[250]]" template="$:/plugins/JJ/multimenu/AliasTemplate"/>
...
#5

Perhaps you could use one list filter to search all :* fields, then within that test for the different conditions with a set of independent if/else statements.

Personally I like to pull out parts of filter and build function to replace them, this makes each filter more readable.

  • The more you can see and read in a single view the easier it can be to debug.
  • I see the same piece of filter being used a number of times, these are great for functions, even if you negate them later eg the - or except:

I don’t have time to rewrite this just now, maybe later if you have not resolved this.