David, Sometimes using the metaphor of folders is very helpful. If you look into how the $:/ and core tiddlers are named you can see how you can structure tiddlers.
It is quite east to choose what I and others call a namespace eg; $:/config or your own $:/database or $:/excerpt than construct a new tiddler name $:/excerpt/$(currentTiddler)$ in a macro, so there is another unique tiddler $:/excerpt/tiddlername for each tiddler if you want. The lookup operator can help you find it or add and remove prefix operators allow you to quickly locate matching tiddlers in these different namespaces. You could excise text into $:/subtiddlers/tiddlername/excisename for example. Of course there is an issue when you rename tiddlers, but there are ways to address this, including a Serial number method I plan to publish after another plugin I am developing. Feel free to discuss further Regards Tony On Saturday, February 29, 2020 at 1:10:19 AM UTC+11, David wrote: > > I'm a progammer and am seeing if using TiddlyWiki might work well for > documenting some of my projects. It seems so. > > I have some SQL code that is a part of one task I'm doing. I wnated to > spawn that code off into another document so that the main one was not > cluttered with so much info that wasn't needed very often. So I used that > excise feature to put the SQL code into another tiddler and I left a link > to that in the main tiddler. I like it. > > The excised code i named "SQL to get Sample Records". > > Then it occurred to me that if I like this and add a bunch more projects, > then that tiddler name is not all that specific, and will probably need to > be improved. If I were in a file system, that sql code might be in its own > folder so that such a simple name would be appropriate. > > So what do you guys do for TiddlyWiki? In a way, these Tiddler names make > it so that everything is, in essence, in one folder. > > I guess I need to perhaps make the name more specific, with a prefix that > resembles the name of the project or task. > > Instead of "SQL to get Sample Records" > Maybe "Customer Design Change 2020 Feb - SQL to get Sample Records", > though long and clumsy, is a tiddler name that will be better as more and > more projects get documented in my TW. > > does that sounds like the best way to go? > What are you guys doing in this kind of scenario? > -- 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/77f12e82-b6fc-441b-ac09-f61ed510ff34%40googlegroups.com.
