I have tiddlers which define tasks, and are tagged as such. Tasks can belong to other tiddlers which are projects, tagged with "project". I currently tag the task tiddler with the project to which it belongs, as well as other tasks on which it is waiting. However, this makes it difficult to distinguish whether a tag is referring to the project the tiddler belongs to or the task on which it depends. If a task depends on a project, then it would be impossible to distinguish the parent project from the dependent project. Therefore, I have been planning to move this information into separate custom fields, "project", and "waitingFor". With the original approach, I could depend on RenameTagsPlugin to ensure integrity if I happened to change the title of a project or task tiddler. But RenameTagsPlugin will not work on custom fields. Therefore, I was thinking to store a different unique reference instead of the tiddler name, so that even if I change the name of a project or task, the reference store in the custom fields would not have to be updated. I think that is what you mean by storing the UUID in the custom field instead of the title. Can you elaborate on that approach? Does TW define a UUID for each tiddler? Thank you!
On Mar 14, 6:01 am, FND <[email protected]> wrote: > Could you elaborate on your use case? It would help to know why you're > storing tiddler references in custom fields in the first place. > > The obvious option is to use UUIDs as tiddler titles, but that of course > makes linking inconvenient for users. Perhaps you could store a UUID in > a custom field, so lookups later use that field instead of the title? > > -- F. -- 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.
