I will try to make a list of some links but this is really the way to go. I play dwarf fortress and have been working with TW and I have found working with fields to be extremely powerful and flexible. There are a lot of widgets that allow you to work with info searched for in fields as well so I would suggest really concentrating your 'learning curve ops' by searching and reading about fields and the widgets that allow you to work with them. Mark's explanation here is really spot on.
On Tuesday, November 19, 2019 at 8:51:50 PM UTC-5, Mark S. wrote: > > There are many ways to put things together in TW. It kind of depends on > how monolithic the structure > you're attempting to create is. > > Here's one way. > > In terms of traditional relational databases, you can think of all > tiddlers that have the same tag > as being rows in a table. The fields of each such tiddler are the fields > of the "table". The title > should be thought of as an ID field, and not, unfortunately,as a title. > Use "caption" and "description" > as the actual title fields. > > Tag/Tables can form parent-child relations via reference fields. So you > might have several items > tagged as "Project". Then you might have several tiddlers tagged as > "Tasks". Each tiddler tagged > as "Task" can contain a reference back to the original project tiddler. > For instance, you might > have a field "projid" that contains the name of the "parent" tiddler that > is tagged with "Project". > > Using nested list widgets, you can present the information in the Projects > and child Tasks > much the way you would in various report tools. > > Project A > Task A1 > Task A2 > Project B > Task B1 > Task B2 > > The display doesn't have to show the tags or the reference fields that are > structuring the data. > > There are other people that would tag each task with the "parent" tiddler, > but that quickly leads to > tag pollution. > > So, there's one approach. It really depends a lot on what you are trying > to accomplish. I'm sure others > will chime in with their thoughts. > > > On Tuesday, November 19, 2019 at 4:59:48 PM UTC-8, Qalisto wrote: >> >> Hello, I am new to TW. >> >> It seems, I should have discovered it long ago. (I had been using an app >> for Windows called *ConnectedText. *But, it lacks the killer feature of >> TW which is single HTML distribution.*)* >> >> I have a question about the strategy for rational and flexible access to >> Tiddlers. >> >> It seems to me that for Core Business interests that it may be wise to >> just create Tiddlers as "info Lego blocks" into a "Core Bus. TW" as Tiddler >> repository. >> >> Then, by using the correct coding or Tagging strategy, to be able to >> extract a list of Tiddlers which one may wish to include in ... say >> "Project A" (while the same Tiddlers may *also* be employed in "Project B". >> >> So, given the bewildering set of system, user, shadow Tiddlers, I am >> wondering if anyone more experienced has a system which will: >> >> (1) Enable a single Tiddler to be coded in a way that will identify it as >> in the family of say "Project A" and also "Project B" if it is a common >> info bit. >> >> (2) Hide that multi-project coding since I will want to compile the >> family of Tiddlers as a business presentation and leave the content "tidy" >> >> (3) And be able to order the extracted Tiddlers from the Core TW File in >> the desired order of presentation >> >> Of course creating an "NY Public Library" of Tiddlers may be unwise. I >> don't know at what point a TW file becomes too fat and thus unwieldy. But, >> I plan to create distinct ones where possible. >> >> There seems to be multiple solutions spread about various user URLs. And >> I am sure I could divine this with hours of research and trial and error. >> >> I just wonder if someone *has been where I want to go *and can kindly >> *share* a shortcut. >> >> Thanks for any help. ## Q ## >> > -- 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/01325482-17f2-4398-b6a4-432b831585e8%40googlegroups.com.
