For anyone who finds this topic via a search, after experimenting a bit it turned out the easiest way to extract the content of a single json plugin file is to use the node.js server version of tiddlywiki. Use the following command:
tiddlywiki --import /path/to/plugin/file application/x-tiddler --savewikifolder /path/to/output/folder Make sure the output folder is empty. The output includes some additional files -- the plugin files will be in a subdirectory of the output folder called plugins/PluginName. I've attached a script I knocked up to make the process a bit easier. This topic can be closed (the original poster isn't able to!). Regards, David. On Sunday, 22 September 2019 11:00:40 UTC+9:30, David Nebauer wrote: > > I'm playing with a script that unpacks a single json plugin file to > individual tiddler files for installing under a node.js server. The script > would also create a plugin.info file and, if necessary, a tiddlywiki.files > file. (Note that TW is not involved in this process - the script acts > directly on the json file.) > > I am only using a subset of tiddlywiki.files functionality at the moment > - just the 'tiddlers' section with the 'file' and 'fields' fields. > > My question is this: is there any way of determining solely from the > contents of a tiddler whether its metadata should be provided via the > tiddlywiki.files file rather than the tiddler's own file? Another way to > put that is: is there an algorithm based on tiddler content that determines > whether a tiddler's metadata is provided via the tiddlywiki.files file > rather than the tiddler's own file? > -- 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/bf3e730e-be9c-49b6-99c2-d3ddcbc9f95c%40googlegroups.com.
tw-unplug
Description: Binary data
