Tony, as you may recall, I've experimented a bit with Joshua Fontany's great JSONMangler plugin and (nested) JSON data tiddlers. I think, the plugin provides the tool you need.
But, after a bit of a learning curve, I found I was able to get it to work and to access and retrieve data. I am not fully happy, though. The main issue I have is that JSON only offers minimum features. It stores data. Period. When you want to retrieve data, they come out in the way you have stored them, unless you want to mimic features in TW normally offered by a *DBMS. E.g. for retrieval in a given sort order, you will need to either use one of the sort functions on the whole data set or create an ISAM feature in TW. As I wrote before, this is a rabbit hole I would be reluctant to jump into. There has been work put into this topic by minds more proficient than me, So I'd rather resort to the work done by them. Also, I don't know, how JSON performs with large datasets, but I would assume at 800 records there won't be too much performance issues. So, for the time being, I will stick to my TW-based solution, but in the long run I feel tempted to try out PouchDB/CouchDB which seems like the natural complement for this kind of problem. Best, Werner Am Mittwoch, 19. August 2020 04:42:56 UTC+2 schrieb TW Tones: > > Folks, > > Has anyone developed a method to create multiple tiddlers directly into a > JSON tiddler? > > *Background* > > I just built a macro to create color swatch tiddlers, more than 800. > > - I will share it soon, once I create some tools for color search and > copy tools > - I did it Using a button containing a list and the > ActionCreateTiddlerWidget > > *What?* > > However I realised since the action create widget is basically handed a > set of field=values it should be easy enough to create such tiddlers in a > JSON file only as JSON tiddlers. > > - It would need an append process > > I will eventually build this myself if there is no response however please > share any previous examples "Prior Art" of doing this. It seems to me as > deserving of a facility in the core so perhaps others have done it better > than I can hope to. > > *Why?* > > - When creating large numbers of reference or data tiddlers they could > be created directly into a json file saving space ?, but permitting access > as shadow tiddlers. While keeping the number of real tiddlers small. > - It could allow an intermediate step from what you choose to make > into a real tiddler. Then delete the JSON when finished. > - It would allow virtual tiddlers to be created from tiddlywiki > content that exist only in the JSON format. > - JSON's are readily converted to drag-able packages, import tiddlers > and plugins. > - JSONS can be interrogated as shadow tiddlers or as data-tiddlers. > > Thanks in Advance > Tones > -- 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/b734e1f6-38b5-43fa-b5d8-97df0dc2432co%40googlegroups.com.
