Mario,
I hope this is the appropriate thread?
I believe you already have the skills we need to use the local storage and
save changes process I proposed elsewhere.
- If I go to a site with the local storage plugin installed, not using
auto save, make it so the only way to reset the dirty flag, thus leave the
website tab is clicking a "logout" process. Thus logout process would (if
possible silently) save the changes with the following filter
[haschanged[]] [enlist{$:/temp/BrowserStorage/Log}] !readme.txt
- This save would in fact be a download to a download folder only. See
below for a download folder name. This is like your backup solution?
- Then if this save can occur silently, like the backup solution you
have already designed (I think), the user keeps using the URL to get to the
site and uses local storage, to close the browser or tab they must use the
logout process (Which could look like the current save button).
- If we can save silently it would not be as intrusive if the changes
backup need only occur when closing the tab or browser.
- Then a mechaisium to detect either first visit (no changes saved yet)
or the possibly rare case of lost browser storage, where the user can
create a new "backup changes" or restore the last saved changes.
- The value being all saves can be in the download folder or below,
perhaps a folder based on the url such that the folder will be unique to a
url, as is the local storage. That is the name determine where the changes
are saved, so if lost the previous save can be found.
- A separate download of the whole wiki plus changes (the default save)
would be needed to move to another save mechanism, local copy or to access
in another browser., or another machine.
- If browsers share the download folder perhaps you can change
browsers on the same machine?
- We could have a "full backup" method, similar to the download, as
well, to restore the whole wiki, even a new one at a public or private
url.
Notes:
- Perhaps cookies are less prone to loss than local storage, perhaps a
cookie could store the backup folder/filename? If not present on current
url/wiki prompt to load from downloads?
Tones
On Tuesday, 1 June 2021 at 22:31:06 UTC+10 PMario wrote:
> Hi,
> I do have a different idea, using the "local storage" plugin, but I want
> to do more tests, since there is a behaviour, that I did see with an older
> version. I want to be sure, that we are really able to avoid data loss.
>
> Will post about my tests soon.
> -mario
>
>
--
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/56767066-ae26-48f4-ac79-090169139da4n%40googlegroups.com.
