Hi Linus,
Thanks for the outline, your structure is much clearer now.
> If I understand your notion of "recursive" filter correctly, one would
> still need something equivalent to x-plore to create a list that can be
> used in further filter runs (in my case, to weed out anything but the
> concepts)?
>
The complexity would be reduced to introducing an appropriate filter that
is capable of doing the recursion... and then returning a flat list of
corresponding (unique) tiddler titles, even though gathered through
recursion. No need to fiddle with "tree" outputs, yet (think x-plore).
What is a bit tricky, if not impossible atm, is that such a filter would
ask for two parameters being filter expressions themselves...
- *travesal-filter*
- a filter defining what nodes to recursively traverse
- e.g. "[all[current]tag[Concept]] [all[curent[tag[Memo]]"
- *collect filter*
- defining what tiddlers to collect during traversal
- defaults to the "traversal filter" but can be different
- e.g. "[all[curent[tag[Memo]]"
The problem with this is that currently there is no way to specify a filter
as a parameter inside another filter. So, I guess, that brings us back to
using something else other than a filter to begin with. Right now, I'm
assuming it would, initially become a javascript macro with the above two
parameters.
Best wishes,
— tb
--
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/9834ca5b-b231-4fbf-bf6d-7df9036d4b2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
