I answered my second question:

<<forEachTiddler where ''tiddler.text.contains("<part definition")' write

'"[["+tiddler.title+"]]: <<tiddler [["+tiddler.title+"/definition]]\>\>

\n"'>>

I still need the answer to the first question, however. Thanks

On Thu, May 30, 2013 at 3:35 AM, Steve Rutter <[email protected]> wrote:

> Hmm... Looking over the information for foreachtiddlerPlugin, it looks
> like it can work directly against another file. Can someone tell me if it
> loads that other TW in memory and parses it, or does it just look at the
> text itself?
>
>
> On Thu, May 30, 2013 at 3:21 AM, Steve Rutter <[email protected]> wrote:
>
>> One of the things I want to do with my TW is to compile report data that
>> we write here at work. I project that we will have about 1000 reports this
>> year, plus our past years. We have about half a page of Word data per
>> report. Compiled, this would not be much data, but I know TW slows down
>> loading when there are thousands of tiddlers. So my idea was to compile the
>> reports into, say, monthly tiddlers, and use parts to separate them. I will
>> have the data entered using the dataTiddlerPlugin. I will then be doing
>> tracking and trending on the data.
>>
>> What I would like to know is if there is a way to dynamically fill in a
>> data template using the data in a part? For instance, let's say I search
>> against report data using the native search. What I want to see is
>> individual search results for each PART found, and when clicked, only the
>> data from that part is displayed in its correct template.
>>
>> Secondly, will the forEachTiddler plugin work against tiddler parts?
>>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to