Ciao TonyM I been playing with Mark S.' PowerShell solution (https://groups.google.com/d/msg/tiddlywiki/tMLfNs1K3JU/gkrGu-ubAQAJ).
My comments are based on experiments with that. TonyM wrote: > > So we can say "this method allows you to open your TiddlyWiki from the > "original file location" (where ever you choose), it saves the TiddlyWiki > in the browsers "download" location, but this file is synchronised back to > the original location? > YES. Though I think "Restored" is a better description since the TW saved it. Its not a sync on latest. Its restore of latest. I think. > When Tiddlywiki is set to save automatically, each time it saves, the next > version filename is used. > > - Will it work for the different browsers? > > YES. That's the point! I works with ANY modern browser. For instance: Open three browsers with the same TW. Download save in each. The latest version gets restored regardless. > > - Need they alternate configurations? > > NO. Footnote: there are small differences in how some Browsers save the version naming. They are easily dealt with in the restore name matching. > > - I assume we need to set *one* "original location", does this need to > be set in the command file? > > Most users, I think will use the Windows "default" downloads location that any browser you install starts with. But, longer term, it should be possible to monitor more than one location if a user has set up their browsers to save to different places. Right now the script just monitors one (by being in it). I think this is an issue of "how tech do you want to get?" But ground zero is one monitored directory. The rest is a matter of further coding. I don't want to load Mark S. up with work when its maybe not needed. His thought about this method is, I think, good. And he needs time and appreciation. > Must "let me choose where I download files" be disabled? NO. But it won't work if you save someplace not being monitored. > > - Can we build this to cater for every Operating system? > > Probably. The back story is that precisely because of the demise of the old methods the browsers had to converge on some kind of consistent method on naming and download directory, whatever platform. Likely an unintended consequence, but basically all modern browsers inter-acknowledge on download saving. PowerShell solution on Windows should be translatable to other OS. The principal of "Restore" is not complicated. Tony, FYI *the only issue I see is TIMING.* The downside of using an external script to native TW methods on saving is that Restore is that you need to POLL the Wiki often to keep contemporaneous. This may be slightly confusing to end-users under some circumstances. Say I monitor with the script my wiki every 10 minutes but saved 5 minutes ago ... if I refresh then the changes won't show. Mark set the default polling in test to 10 seconds. I'm not sure I'd use that but I think that is part of the reason--so its very likely the auto-restore is in line with expectations of what you entered in the wiki. Best wishes Josiah -- 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 post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1847fc18-abb6-491b-b0f3-da0247201d8a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
