Saq, I just got to try this now I am back at my desktop and looking good. A Few quick comments on your latest notes.
Interestingly before looking I expected the tiddler titles to actually be the text in the bullets. I would be fine with this even. The actual text field could be used in subsequent lines since bullet points naturally are "points" or list items. In which case the title of the subtiddler is somewhat obvious, and in fact normally contains the words that helps one determine when the items is needed and where. I would just add whatever we want to call a bulletstream it is a method by which to outline, and the main feature of mind mapping apps is not really the visualisation but to be able to make a root above the root and other relationships as needed and quickly, before the though disappears. I see bullet stream as capable of this. > 1. do nothing and use an external plugin like Relink (current > situation, but its a non trivial plugin dependency) > > I agree with this strategy but wonder if a relink equivalent should be introduced to the core, as fundamental as it is, even if it is selectable. > > 1. make a core pull request to get a rename tiddler hook that is > usable (the current one isnt) and handle the rename updates > > That makes sense for this and other future use no matter what. > > 1. rework all relationships between tiddlers to be based on UUIDs > rather than tiddler titles. This is entirely doable and would be rename > resilient, at the cost of longer and more complex code. The mapping from > child tiddler to parent is already UUID based, the reverse could be as > well, it just makes lookups harder. > > Having explored the creation of compound tiddlers, I have considered related issues for some time. I also build a simple UUID method that works comprehensively. I actually believe it can be quite simple. There are even techniques to make lookups simple. I will give this more thought after reading and playing more. > > 1. Use the "list" field and the core ability to update... except that > we will at some point clash with other things (like tags) using this field > as well. > I would prefer to have the option to leave the tags untouched and thus > usable for other purposes. > > I like this approach to leave tags untouched. But tags are just an example of a kind of list anyway. If the root tiddler contained a list of tiddlers, Names or ideally UUIDs or as I have come to realise they need not be as universal as one may think, current tiddler titles are not universal. What I call a TSN Tiddler Serial Number can be created as needed as long as there is no ambiguity, they can be short, and collected together like a list of tiddlers. Given a list draggable tool they can be reordered. Perhaps even an alt-tag field of sorts. A few simple macros could work like the qualify macro to dish out a unique id as needed, or provided a TSN display the title of the tiddler that owns it. I will look at this a little further. Take your time with your health, but it sounds like it is sometimes your source of inspiration, if not the time you build things. Love your work Thanks again Tony -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/271ab1df-13d8-4762-804b-27c9f316acae%40googlegroups.com.
