I'm not sure if this is important, but I'd like to mention a couple of use-cases.
1. While using IncludePlugin, one can have two tiddlers with the same name in different documents (say, "Notes"), and also can desire to use both (for instance, include "Notes" from a document about web- technologies into the "Notes" regarding TiddlyWiki). In this case it's enough to distinguish tiddlers by their *source*. Here are some though. It is desirable to have a "syntax" (formatters and macro definitions) such that each link or transclusion macro can have a target outside the document (smth like [[...|Notes]]@webTech like in TiddlySpace, or [[...|Notes@webTech]]) and a "destination table" |webTech|./web-technologies-learning.html| |...|...| which allows, besides other things, to *move* or rename a webTech destination or even *change it to another document*. In this aspect, it is about aggregation of tiddlers, not exactly their distinguishing. Problems with distinguishing will occur if one would like to make a non-distributed TiddlyWiki document i.e. import the external "Notes" tiddler into the document. 2. Second use-case, or rather prospective is semantical versioning of tiddlers. There's still no for managing system for multilangual tiddlers or author's/public versioning of content. While this can be done (rather awkwardly) using different tiddlers for each "version", it creates many eclectic constraints and other problems, it seems that the only proper way to implement such things is to have multiple text areas in each tiddler. It may be useful to keep this second one in mind for the protocal design. -- 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.
