I knew, that you don't like, that some tiddlers are listed twice. ... But for me this is a feature ;)
I did play a little bit with the macro. I did create a brainstorming tree. ... I found out, that after some refactoring one "child" tiddler had many "childs" itself ... So it actually should have been a parent :) - The thing to do is, just remove its parent tag and you are done. The list is recreated in a new way. ... - Some tiddlers actually made sense, for me, to be listed twice. The advantage here is, that you don't need a management UI other than tags. ... There is a reason, why I wrote: > If you combine tags and fields, you'd have endless possibilities and > complexity :) > As you found out (see your concept) combining fields and tags adds complexity. .. The relations are simple (for human brains), but to UI to make handling it convenient isn't there out of the box :/ And it adds some more questions. ... where to use fields, where to use tags ... What if a field becomes a tag or vice versa ... .... If you want to control the structure of the tree, you could use a field named: parent. Only the field "parent" is used to create the tree. Every "tree-tiddler" must have only one parent The root is created using tags. Tiddler lists are created using tags I think this concept would be easy to create and manage (by hand). I'm not sure, if the macro code will be easy :) let's think a little bit. -mario -- 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. For more options, visit https://groups.google.com/d/optout.
