For what it's worth, I have a wiki that's a copy of my company's ActiveDirectory with about 30,000 people in it - one tiddler per person. It is a little slow but it works. If the issue isn't performance, but rather the "polution" one idea might be to "hide" them with a prefix - like $:/book/chapter4/section6/subsection23 per your example. Tiddlers with the $:/ prefix are automatically hidden from most general areas of TiddlyWiki.
I've also played with data tiddlers for similar things and performance is much better, but it makes working with properties/fields more difficult, so there's a tradeoff. If there was such a thing as a datatiddler that allowed multiple fields/columns (like JSON), that would be a game changer, but alas even datatiddlers as they are seem to be on the chopping block here from what it sounds like - still supported but nobody's interested in developing them further. On Tuesday, April 27, 2021 at 9:42:12 AM UTC-4 Cs Molnar wrote: > There is something I want to achieve with TiddlyWiki but I don't know how, > so I hope one of you can help me. > > My problem, in a generalized way, is the following: I want to take reading > notes from a book in tiddlers. The book has chapters (about 60), every > chapter has on average 20 sections, and every section has on average 30 > subsections. This makes around a total of 35000 subsections. > > In my tiddlers I will refer to specific subsections. Later I want to be > able to list all tiddlers which refer to a certain subsection. Also, I want > my references to be links to the content of the subsection on the internet. > (The book's subsections cannot be included into my TW, but they are > available on the internet.) > > Of course, the easiest solution would be to create one tiddler for every > subsection and insert links like [[Chapter4_Section6_Subsection23]] into my > notes. This way I could find every reference to a subsection. But this > would mean creating 35000 tiddlers (equivalent to 35000 files in my TW on > Node.js) to cover all subsections. Even if I didn't create them, I would > have 35000 missing tiddlers. This approach would heavily pollute the list > of my tiddlers. Every time I would use the $list widget, the 35000 existing > or missing tiddlers would come up. > > I hope someone has a good idea to save my TW from this pollution, but > still retain the possibility to search for references. I thought that I > could develop a custom widget in Javascript which would store the reference > list in a JSON tiddler. I'm experienced in JS programming but have less > knowledge on TW internals, so I'm not sure if this is the best solution or > is it overkill. > -- 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/b40e4a6b-0e9f-46ab-b139-c7f977c7a5c6n%40googlegroups.com.
