Hey David,

I do use something like that, but I seperate links, tags, and what is 
"related". I currently used a related to field to handle this, but that has 
the problem that if I want to add another tiddler to that relatedness, I 
have to edit ALL of the tiddlers it is now related to.

On Thursday, June 7, 2018 at 11:01:59 AM UTC-5, David Gifford wrote:
>
> Why not use a tiddler tagged $:/tags/ViewTemplate, with this:
>
> <$list filter="[all[current]backlinks[]sort[title]]"><$link><$view 
> field="title"/></$link> </$list>
>
> Then anything that links or tags to the present tiddler will show up in 
> the tiddler as a related tiddler. There wouldn't be a separate tiddler 'A 
> relation', but between tagging and backlinking you would be able to see all 
> related tiddlers. And it would change as you change the links.
>
> On Thursday, June 7, 2018 at 9:34:01 AM UTC-5, Diego Mesa wrote:
>>
>> Hello all,
>>
>> I've been thinking a lot recently about how to handle tiddler 
>> "relations". That is, I have some tiddlers that are *related* to others, 
>> but not necessarily through (my version) of a tag relationship. I first 
>> just started typing out a related section in each tiddler like this: 
>>
>> Tiddler 1
>> -------------
>> ...
>> my content
>> ...
>>
>> !! Related
>>
>> * [[Tiddler 2]]
>> * [[Tiddler 3]]
>>
>>
>> I quickly got tired of copy/pasting this into tiddler 2 and 3, so I 
>> turned into a field, where each tiddler has a "related" field with the 
>> names of tiddlers its related to. If this field is present, its 
>> automatically displayed at the end as a list. 
>>
>> I am still *building* and *learning* and so these relationships change. 
>> Say I want to say that they are all now related to a Tiddler 4. I have to 
>> now go back and make changes to 3 tiddlers. As the process continues this 
>> gets cumbersome. 
>>
>> So I thought, well I could just have some kind of tiddler like this:
>>
>> A Relation
>> -----------
>> * [[Tiddler 1]] 
>> * [[Tiddler 2]]
>> * [[Tiddler 3]]
>>
>> And then just go back and change that tiddler as the relationships of 
>> that group change. This system is nonoptimal though, as:
>>
>>    - What does its title mean?
>>    - With this setup, every single time a tiddler is opened it has to 
>>    search ALL RELATION TIDDLERS and see if it's listed in any of them. This 
>>    doesnt make sense! 
>>
>> Im envisioning some way to enter a new relation, and upon saving in this 
>> one tiddler, it handles populating the related field somehow. 
>>
>> Anyway, this is all just some random thoughts on this. 
>>
>> Does anyone have any better ideas/systems for managing this?
>>
>> Thanks!
>>
>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/12cf0143-7a6f-4042-82b6-799c1524eb5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to