These keeps coming up so I am going to say this again. A progressive web app can't save to the locally in the sense used in this thread. it saves to the browser cache, it has no more access to the local file system than we already have. if it did then we would use that mechanism to save and none of this would be a problem. Delivering tiddlywiki as a progressive web app is going backwards as far as saving is concerned, tiddlywiki is set up so that you can always use the download saver, PWAs save to the localStorange which is just dressing up the browser cache.
LocalStorage is NOT the local file system, it is the browser cache. It doesn't solve anything about our saving problems. Progressive web apps don't have any privileges than tiddlywiki doesn't already have. Tiddlywiki can either 1 - put the save in the core like all of the other savers it already has in the core or 2 - put the saver in a plugin and use the plugin library mechanism to distribute it. The server component CAN NOT be delivered as a progressive web app because if it could you could directly put things on the file system from a browser and we would just use that mechanism to save and none of this would be a problem. -- 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/169305c1-b592-4834-bcae-517e95d8206c%40googlegroups.com.
