Hi Tony,
thanks for engaging in the discussion.
I do not need the browserstorage - but other users of my wikis (my
students) would need it.
I do not need it because my edits are saved on the server. And I always
want to work with the newest version on the server. And I do not want
deleted and renamed tiddlers to come to life again.
My students sometimes are buffled, that the changes they made are not
saved and it is unpleasant to tell them, that they are lost unless they
posted them to me.
So I need a construction that prevents this ... without interfering into
my editing.
Best wishes Jan
Am 16.04.2020 um 12:18 schrieb TonyM:
Jan
I don't Actualy understand your perceived problem. The local storage saves and
retains the updates in the browser and if you return to the same address it
will be there although some cases of possible loss. To combat this I thought of
a export button that exports changes as a backup, where most users can't save
to the original file only a backup.
If you try and leave a site even if local storage is up To date it will warn
its not saved.
So I think its operation my be different to what you think. I have researched
this a lot so when its clearer happy to discuss further.
Regards
Tony
--
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/5E98BA0A.9050401%40googlemail.com.
