For years, I have written a large amount of autobiographical, ideas and such using the mind mapping (hierarchical) program FreeMind. In transferring the data from FreeMind to TW5 I came up with the following scheme to retain the hieerarchical nature of the data, which though not ideal, does put the data in context, making navigation among related date quite easy.
For example: to represent a node (tiddler) named "CMU1 Staff GUI Desgn People" I have put, directly under the Tags the following: NS <#NS> ⬅︎ Schooling <#Schooling> ⬅︎ Actual Schooling <#Actual%20Schooling> ⬅︎ College <#College> ⬅︎ Carnegie Mellon University <#Carnegie%20Mellon%20University> ⬅︎ CMU1 <#CMU1> ⬅︎ CMU1-CAT <#CMU1-CAT> ⬅︎ Took at CMU1-CAT <#Took%20at%20CMU1-CAT> ⬅︎ ◉ ● Brad Meyers <#Brad%20Meyers> ●Nicholas Spies <#Nicholas%20Spies> Each is a link that the arrow (which could have easily been "/" as in a file system) points to is a tiddler that are based on the root "NS", that is myself. The large dot represents the current tiddler, whose title is perfectly evident at the tiddler title, while to the right of the dot are the first level of subtopics , that happen not to be realized (yet) as tiddlers, namely two people who attended this staff seminar on GUI design: Brad Meyers and myself, who are at equal levels from the current node/tiddler, because at this point I am just trying to reconstruct who attended this semester-long seminar. Perhaps later I will structure the seminar, putting Brad Meyers, the leader of the seminar on his own level, with attendees at a lower level, each with their (assigned) topics and presentations beneath each participant, etc. If I were to realize this as tags, I would have to order them from left to right, which I believe is possible (but don't know where I do it), and use the top item of each tag to "walk" back down to the root. Under each tag pull-down menu there would be a listing of every tiddler containing the tag, but the order of the hierarchy would be lost because the menus are alphabetized. There is likely some way to fix this problem too, but it is not at all evident where this type of ordering takes place, either. In the end, it seems that TiddlyWiki is just not prepared to deal with this sort of organizational paradigm without at lot of behind-the-scenes manipulation of meta-data to order tags and their contents, taking more time than the method I have devised, although far from perfect, at least works and is more or less self-evident. It suggests that there could be another layer of qusi-tags, shaped as they are but with an arrow to the left, which are simply links to some previous tiddler in a hierarchy of tiddlers, and then another shape, perhaps incorporating a bullet, to indicate the subtopics of the current tiddler. Then again, I may be entirely wrong on this score, and would like to know what the TW way, that is already implemented, of solving this problem might be . BTW: I find it very annoying that tidder fields are only one line, because their contents may be many lines, making it necessary to copy and paste them into a text editor to even see their contents, much less to edit them. For development, such fields could be multiple lines, while for distribution they could easily be hidden from view, it they are perceived to be an eyesore. --Nick -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
