Hi Dyllon,
> I wrote a small module for saving using the Chromium file system API (which > is in the process of being standardized). > > Example TiddlyWiki 5 Saver Using HTML 5 File System Access API (github.com) > <https://gist.github.com/slaymaker1907/7a04a6188179bfe113b122b1f51e22b5> Great stuff, I’ve been following the File System API with interest, and would be keen to get a saver in the core once the spec settles down. Here’s a link for those unfamiliar: https://web.dev/file-system-access/ <https://web.dev/file-system-access/> I don’t know if any other browsers are planning to implement the API. It seems like an obvious requirement for ChromeOS, but perhaps other browsers will have less incentive to implement. > The first time a save action is triggered, it prompts for a save location but > future saves should go to the same location. > > It's a bit dangerous because if saving fails, there is no way AFAIK to > disable the saver after it loads. I would be interested to know if anyone > knows a way to disable a saver after it has already loaded. I think you’re already following the correct approach: for the save() method to synchronously return false if the save cannot proceed so that the next saver in the cascade gets a chance. Another thought with respect to the File System API is that it may be possible to write a syncadaptor module so that we can support TiddlyWiki folders containing individual .tid files in the browser. Best wishes Jeremy -- 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/D96AF54A-0DAE-44E6-A788-4ADE90164FAC%40gmail.com.
