Nick et al,
I have always wondered if this problem can be turned upside down.
- Load a prepared wiki either from the internet or by opening a local
file (the base wiki).
- In both cases you can make use of local storage and returning to that
(address) or tab, the original "file" and in browser changes will
(typically) be there.
- However since this is a little brittle;
- Export the changes from the Wiki in the browser to a file, eg
download the changes (at the end of a user session, or occasionally)
- Include in the base wiki a mechaisium to check if its has any
changes from base
- If on loading there no changes from base, it is either a new
wiki or has lost its changes, prompt to load from local backup (of
accumulated changes only)
- Anything that can be done to download or upload from a known
filetype or location will make this activity smoother.
- If you know where this should occur on a particular device the
base wiki can provide the instructions so you do not have to remember.
- Arguably any local, or internet source, or backup location could be
used to store the base wiki and changes backup, with the whole wiki
remaining in the browser and the ability to encode the backup location and
automate restore if changes are lost.
- If the changes only ever take place on the one device this should
be a safe bet.
- Other opportunities exist for multi-device access, but by definition
they more likely to be online solutions.
Regards
Tones
On Sunday, 6 December 2020 at 04:15:34 UTC+11 Nick wrote:
> Thanks to all, It seems SWs' are really not the way forward. The 'offline'
> feature was the appeal of TW, but as an app on my home screen, the offline
> function is not working. It does not open from files either on IOS. Its
> works in apps like quine but I need it to be its own app. Maybe i've missed
> something, but there must be a way to view a TW file offline on mobiles
> with only the .html file"?
>
> Thanks
> Nick
>
> On Saturday, 5 December 2020 at 16:36:05 UTC jeremy...@gmail.com wrote:
>
>> Indeed. Service workers were intended to help re-engineer existing
>> server-based applications to work offline. The main feature is a background
>> thread that can fake network requests when the system is offline. It still
>> uses the same LocalStorage as an ordinary web page. So there’s not really
>> anything to be gained for an application like TiddlyWiki that was designed
>> from the ground up to work offline. It’s a shame.
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>>
>> On 5 Dec 2020, at 15:52, Saq Imtiaz <saq.i...@gmail.com> wrote:
>>
>> I have similar feelings about service workers as Jed...
>> That said, I know LinOneTwo has done some work with service worker and TW
>> but I am not familiar with the details:
>> https://github.com/linonetwo/tiddlywiki-plugins
>>
>> --
>> 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 tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/d9724b43-6651-48f9-b966-a4af79f97853n%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/tiddlywiki/d9724b43-6651-48f9-b966-a4af79f97853n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>>
>>
--
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/76fdb690-7b0a-4977-88c8-e3ad186f7db8n%40googlegroups.com.
