There is discussion on the other list about augmenting Browser specific "Save" via "Restore from Download". The advantage is it should work for ANY browser.
And, importantly, it should work for TWC JUST AS WELL as it does for TW5.
The idea is a bit different than save from TW itself.
These two threads show the work done so far and gives some idea of how it works ...
https://groups.google.com/forum/#!topic/tiddlywiki/s40q_QZUenA
https://groups.google.com/forum/#!topic/tiddlywiki/tMLfNs1K3JU
Currently its only for Windows, in early testing. But should be easy to extend to other platforms.
Please comment into either thread if you find it relevant to TWC!
Best wishes
Josiah
I'll post again what it's better documented :-).
All it does is copy back from "downloads"--i.e. you save in any browser you want and an external script "restores" (i.e. copies back) the wiki.
In testing its proving good. I got it working for 5 different browers.
Best wishes,
Josiah
That would be good. Its proven very robust for Firefox with TW5. Its backup system is also excellent as it uses a version of the "Towers of Hanoi" rotation--means you get good coverage without needing excess backups keeping.
Best wishes
Josiah
I'll post again what it's better documented :-)
I wrote a kind of overview of the "universal restore" method (Windows only as of now) here: https://groups.google.com/d/msg/tiddlywiki/tMLfNs1K3JU/ehZZAUP9BQAJ
Maybe how it works is a bit clearer?
Best wishes
Josiah
I'll write a procedural explanation.
In a few days.
Best wishes
Josiah
This threads title does little to promote this great idea. Which I only now understand because I spent a little time working through the conversations. I know much of this has being said but its being in discussion rather than statements.
Please let me try
When using the default save mechanism in any browser, you can save changes resulting in a download of the whole Wiki, having an automatic process on your computer, the wiki can then be copied back to your original single file wiki. There by keeping the original upto date. This is done by running a monitor and copy process in your local computer.
Open a tiddlywiki.html file (by another name) using your local file manager and it will open in your default browser. Without any other save mechanism in place, Each time you save, the browser will download the latest version of the wiki into your downloads folder. This means the updated version is not saved over the original version you opened, but you have a copy of the latest version.
(As I understand it) Mark S solution is to run a batch process on the computer to take any updated wiki copy in the downloads folder and copy it back to its source wikifile, thus keeping the original up to date.
My View on this
Josiah and Mark are right to think this could be a ground breaking way to manage wiki saves. Mark has done a good job of building a Powershell to do this. We can write batch shell scripts for every operating system and share these quite easily.
Personally I think an executable program to do the same, or even just install and help configure, may be a better option in time, allowing it to be installed Quickly and a version for each Operating system made available. These executables my just create the correct scripts.
Although this process seems somewhat universal it does expect a certain behaviour from the browser(s) which could actually change in time. We need to monitor this and add additional methods if these change.
Love your work
Regards
Tony
https://classic.tiddlywiki.com/archive/
2.6.0 is listed and (apparently) available.
Is it possible that your 2.9.2 didn't upgrade correctly? Is it worth trying to upgrade it a 2nd time? (assuming you have backups) What plugins are you using? Is there anything about your TWC's name (spaces, non-latin characters?)
Good luck
My own TWC file version 2.9.2 (size: 4.96 MB) doesn't save as expected: instead of downloading the file Chrome fails with a ''download failed - Network error'' message
>Is it possible that your 2.9.2 didn't upgrade correctly? Is it worth trying to >upgrade it a 2nd time? (assuming you have backups)
Tried upgrading my other TWC file. The upgrade seemed to work ok but Chrome still fails with the same error. Btw by upgrading I mean opening a current TWC and importing all tiddlers from my original file as the internal upgrade mechanism doesn't work
>What plugins are you using?
A number of them, will make a list or a print screen. However I have tried disabling them all in both TWC files to no avail
>Is there anything about your TWC's name (spaces non-latin characters?)
Not really. All latin, no spaces. The tiddler content is in Greek but I don;t suppose it's relevant.
>
> download saving was introduced in TWC somewhere near 2.8.1 (well, some preliminary implementations were there in 2.8.0 but those were not.. enabled, let's put it this way), so the behavior of 2.6.0 is an expected one (I'd recommend to upgrade it, let me know if that's not acceptable for you for some reason, I can provide some alternatives).
Upgrading is not a dealbreaker.
>
> My own TWC file version 2.9.2 (size: 4.96 MB) doesn't save as expected:
> instead of downloading the file Chrome fails with a ''download failed -
> Network error'' message
>
> That's unexpected indeed. Have you tried disabling plugins and saving without them?
Yes, in both TWC files.
>
> By the way, if you are using FF 67, you may want to try my adaptation of Timimi. Actually, it's quite possible to adapt it to Chrome, I've already started that journey, but unfortunately haven't finished it yet and don't expect resuming it before the 15th of July (but if there's anyone willing to help, I can share the fixes I've found already).
Sadly I am not a programmer, just a tiddlywiki enthusiast, so I can't help with that. Thank you for picking up Timimi for Chrome, the 15th of July is just fine
>
> Finally, saving in Chrome is also possible if you use one of server-side savers: there's at least MainTiddlyServer by me (discussion), Tiddly-node-saver by James (thread) and minimalistic nwTWcSaver by Okido (thread).
Will try that
> Thanks for sharing the thread.
Thank you all!
sklpns
the internal upgrade mechanism doesn't work
downloading the file Chrome fails with a ''download failed - Network error'' message
https://groups.google.com/d/msg/tiddlywiki/3IR6in7Zqo4/jz3oIM85AgAJ
Possibly a Bash script would work on Android/Termux. The problem with Android from 5+ on is an increasingly more restrictive permissions model. This is why most solutions for Android going forward will probably be actual Android apps. I don't think Timimi can run on Android, can it?
EVERY approach to saving has some limitation. For some reason, people see the limitations of this approach more readily than the limitations of a method that only works on certain versions of a particular browser, or that requires an executable to be installed on a machine (a security violation in some workplaces). This approach is only one step more complicated than the existing download saver mechanism.
Thanks!
Mark S.
>> Yes, a repo would be a good idea eventually. But there hasn't been exactly an out-pouring of enthusiasm ;-)
Ciao Yakov
Its a good idea. But I think the preliminary scoping can happen without one.
Mark S. is correct that the thread in the TW5 group has been widely read yet only 3 people have commented in it :-). So there isn't yet much incentive to make one.
Mark's script works well on Windows. I been playing with different ways of invoking it. (e.g. https://groups.google.com/d/msg/tiddlywiki/tMLfNs1K3JU/brxTjLh9AgAJ)
For my personal use it basically gives the utility I need. But for wider use there are issues that need exploration by others too.
Best wishes
Josiah
apologies for not responding for so long, got caught up with exams etc
Yakov
downloading the file Chrome fails with a ''download failed - Network error'' message
That's actually weird because TWC core doesn't contain such an error string. Is it shown as an alert or as a TW message?
>It seems to be an alert produced by Google Chrome-see screenshot
If it's ok for you, you may send me your TW via a private message and I'll try to debug it. If you minimize its content and plugins (so that the problem is still reproducible), it would be even better because I'll be doing that anyway to find out the cause.
>Thank you very much Yakov! I'll try to prepare a Minimal Test Case. Unfortunately the normal file contains other people's data so I can't freely share it. 90% of my wiki are tiddlers containing custom forms (using Form Tiddler Plugin). So far it seems that the file saves in Chrome if you remove all these tiddlers (!) plus all the system config files (!)
Again, thank you all very much
Best regards,
sklpns