Hi Erwan,
> Yes, thank you Tobias for understanding and formalizing my idea!
> Should we open an issue about that?
>
I think we should, but let's go one more round beforehand, perhaps.
Now I'm beginning to think that it should *not* be a filter of its own but
rather a flag (/suffix) to *any* available sort filter that instructs it to
sort by the evaluated operand, e.g.:
{{{ [sort:eval<sortfilter>] }}}
In other words:
Sort the input elements by the output of evaluating the specified operand
as a filter expression.
Equivalently:
{{{ [sortcs:eval<sortfilter>] }}}
etc...
Not sure if an "evaluated operand" would be relevant for other filter
operations other than sorting and whether we could / should devise a syntax
that always does evaluation, no matter what filter operator.
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/a6d40057-9187-4b10-bb6f-7fb9dc52502f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.