On Sunday, March 24, 2019 at 3:58:40 PM UTC+1, Yakov wrote: ... > in the latest release of TiddlyWiki Classic I've fixed the upgrading > engine and now it's time to deal with saving more consistently. That's > where I'd like not only to ask about some dev aspects but also discuss some > conventions and create docs for consistent support of saving both TWC and > TW5. >
Some basic info about savers can be found here: https://tiddlywiki.com/dev/#Saver If you have a closer look at the implementations <https://github.com/Jermolene/TiddlyWiki5/tree/master/core/modules/savers> - tiddlyfox.js ... outdated, but the mechanism is the same. - beaker.js ... new saver using the dat-project - put.js ... WebDav PUT saver. IMO this info should be enough to create your own simple saver. ... I think the upload.js used a php server side. If a "save action" is triggered, the core uses the saver.canSave() info to check if the saver can be used at all. saver.info() returns the saver capabilities and the priority. If several savers are able to provide the needed save action, the saver with the highest priority wins. ... ATM "There can be only one <https://www.youtube.com/results?search_query=there+can+be+only+one>!" have fun! mario -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/0b8545dd-259b-467c-afb9-9d8be5bc04a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
