> Thanks for your idea! But wouldn't that run into the same issue mentioned
> in the linked post - massive overhead each time the script is run?
I think the problem with FET is that writing this into its code means
it would have to parse every tiddler for parts EVERY time FET runs for
any purpose.
This code does go through the text of each tiddler once every time it
is run (presumably, when you open an "aggregation" tiddler). But
that's really not such a big deal, at least not with any reasonable
number of tiddlers. I don't have any trouble with something like this
in a TW with dozens of tiddlers to look through. The overhead could be
reduced by using tags (maybe "project") to indicate tiddlers where the
desired text could occur and then store.getTaggedTiddlers("project")
to limit the collection being searched.
Eric's solution does virtually the same thing (still sifts through all
the tiddlers), but I do like it better. Since a section would work as
well as a part for your purposes, you don't need to actually go
through the text, and you can eliminate the RegExp search as well as
the PartTiddlerPlugin if you don't need it elsewhere.
--Jon
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
