mirror of
https://github.com/Jermolene/TiddlyWiki5
synced 2024-11-09 19:39:57 +00:00
5aa3646df5
* Initial Commit * Fix plugin library URL * Need to set plugin library location for prerelease * Styling tweaks * Docs * Add tests that the core plugins all have a valid stability field |
||
---|---|---|
.. | ||
config | ||
plugin.info | ||
readme.tid | ||
savetrail.js | ||
settings.tid |
title: $:/plugins/tiddlywiki/savetrail/readme This plugin causes TiddlyWiki to continuously download (as a JSON file) the contents of any tiddler that is manually changed by any of several means: * Confirming an edit * Deleting tiddlers * Imports * Renames/relinks * Optionally, typing in draft tiddlers can trigger a download Where appropriate, separate 'before' and 'after' files are downloaded. Configured correctly, the browser will download the files silently in the background, and they can be used as a backup in case of accidental data loss. ''CAUTION'': Using this plugin will generate a //lot// of files in your downloads folder! Some points to watch: * This plugin is pretty much unusable unless your browser is set up to download files automatically, without prompting for the location * Automatic file downloading doesn't work in all browsers - in particular, Safari and Internet Explorer do not currently support the [[necessary HTML5 feature|http://caniuse.com/download]] * Be aware of the privacy implications of leaving a plaintext trail of all of your edits. You should only enable this plugin on computers that your trust and with content that is not sensitive * The plugin uses the tiddler title plus a timestamp to generate a filename for the downloaded file, but some browsers ignore the specified title and generate their own title for each downloaded file Other points to note: * By default, after a draft tiddler has been modified the plugin waits until at least one second has elapsed since the last typing before it attempts to download the tiddler. This reduces the number of times that rapidly changing tiddlers are saved * This plugin can be used with both the single file HTML configuration and under Node.js because it is independent of the usual saving and syncing processes