This question stems from a post I made here <https://groups.google.com/g/tiddlywiki/c/60IxH2QoBDY/m/kYWGzpIRBgAJ>, but I'm also curious about the more general question so I thought I'd make a separate post.
*General question:* I can't think of anything that you can do with JSON tiddlers that you can't do with normal tiddlers, so I'm curious where it would make more sense to use JSON? Actually I can think of one thing: tiddler fields have character restrictions. But this doesn't seem like a big deal. It seems outweighed by the fact that we have much better tools for manipulating normal tiddlers. *Specific case:* My specific case that triggered this question was that I created a button to store "history" for particular tiddlers. The button essentially creates a clone of the current tiddler with the title <currentTiddler>/history/<timestamp>. Since I anticipate creating a lot of "history-tiddlers", it occurred to me that another approach would be to just store all the history data for a particular tiddler in a single JSON tiddler. This feels a little neater, but more specifically I wondered if there were any clear advantages to either approach? Will storing all history for a tiddler in a single JSON tiddler be less of a drain on performance than using lots of individual tiddlers? -- 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/5b2d5326-b0ef-4723-8a33-8597f92a8c99n%40googlegroups.com.
