Tones, thanks for putting this together, but your solution is slower than mine as far as I can tell (no easy way to instrument that since it has a very different number of filters, but the difference is apparent from clicking around a bit).
Saq, I can't get your filter to work and I can't see how it would work in theory either now that I look at it – the !!condition in the subfilter is getting the condition field on the tiddler in which the tab list is being rendered, whereas it needs to be the *tab* tiddler that's coming in on the input of the subfilter operator…right? Or am I just being dense? In my :reduce version it has a different meaning because :reduce actually resets the currentTiddler variable to match the input value currently being processed <https://tiddlywiki.com/#reduce%20Operator>. With the additional optimization work I did the other night, including optimizing the filters on each tab as Saq pointed out, I would say it's now performing acceptably with my current version, if only barely on a slower computer. So if nobody has any other ideas, I think I can leave it where it is for now. -- 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/d31f9d76-26f9-4c63-8e12-167e42ae11a9n%40googlegroups.com.
