To emphasise that the discussion about deprecating data tiddlers is part of the long term conversation about the evolution of the core of TiddlyWiki. As a user, there's nothing to worry about thanks to our commitment to backwards compatibility.
And to clarify further: "deprecated" in this context doesn't mean that something goes away, just that we recommend against using it for new work. Best wishes Jeremy -- Jeremy Ruston [email protected] https://jermolene.com > On 19 Aug 2019, at 12:31, Jeremy Ruston <[email protected]> wrote: > > Hi Tony > > “Data tiddlers” refers both to tiddlers formatted as JSON and those formatted > as a dictionary tiddler. > > Best wishes > > Jeremy > > -- > Jeremy Ruston > > >> On 19 Aug 2019, at 12:26, TonyM <[email protected]> wrote: >> >> Jeremy, Hubert, >> >> I assumed data tiddlers tends to refer to DictionaryTiddlers rather than >> JSONTiddlers >> Perhaps JSON tiddlers is the way to go. >> >> And you can extend JSON handling using Joshuas JSON Tools for Tiddlywiki >> 5.1.20! if you want to get really serious. >> >> Regards >> Tony >> >>> On Monday, August 19, 2019 at 7:15:35 PM UTC+10, Hubert wrote: >>> Hello, >>> >>> With data tiddlers being deprecated, would anyone suggest a best practice >>> approach to storing large data sets in the flat format key:value? I know >>> that Jeremy suggested plugins but I could not find anything remotely >>> related. >>> >>> Among other things, I'm using TW to log my cardio workouts. I now have >>> thousands of dictionary entries relating to cardio workouts as well as >>> their types and durations that I dynamically retrieve to generate stats, >>> summaries, forecasts and SVG charts. And so I was wondering if there's now >>> a better option to have the underlying data stored within TiddlyWiki other >>> than in a single data tiddler. I would obviously wish to avoid a scenario >>> where each data point is a single tiddler. I would also like to avoid >>> plugins because there's no warranty they will be maintained forever. >>> However, if there's a "clean" solution (perhaps with the use of system >>> tiddlers) or anything else generally considered "better" than data >>> tiddlers, while still being as future proof as possible, then I'm open to >>> suggestions. >>> >>> Thank you (and apologies for the wall of text). >>> >>> Regards, >>> Hubert >> >> -- >> 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/38d413bb-2f93-4803-af11-0373df29eecd%40googlegroups.com. -- 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/55DA9270-AE6E-496A-A0CB-9394005F9AE9%40gmail.com.
