Having used this now for a little while I want to comment that I think the
general idea is really good!
It works.
The main advantage is it works with every wiki scenario the majority of
users would ever use. Just one method to learn. No plugins needed.
Works with every modern browser. Not limited to Firefox or Chrome. ANY
browser. ANY version of TW or TWC.
This is very good in:
(1) not having to be browser focused [why should a user need to choose a
specific browser brand? They should not have to!]
(2) Works the same way for all browsers.
In tests it has proved robust.
It builds off the "default HTML5 saver" fallback method--meaning modern
browsers that save to the "downloads" folder. The work is in how *it
auto-resurrects saves*.
There are a bunch of directions this could develop into something that
could go further.
(*But that is unlikely to happen unless it gets tried more by more people!*)
At the moment its two men and a three-legged dog using it.
And, it could, in theory, be used as a complementary method to other
approaches (TiddlyDesktop, Timimi, PMario's saver). Its not in conflict
with other approaches. Its additive and freeing.
The approach is focused on "Restore" rather than "Save", which is left to
the browser.
By focusing on "Restore" it solves a bunch of problems. That also opens the
way to a "pan-restore system" that could, in principle, work with different
existing backup systems used in TW.
*Its a different approach to keep your updated. *
One that has great merit because of its wide functionality. And deserving
exploration.
At the moment its a Windows based solution only, but could be converted for
Mac & Unix pretty easily by the look of it.
Best wishes
Josiah
On Monday, 20 May 2019 23:41:19 UTC+2, Mark S. wrote:
>
> I'm not a PowerShell aficionado, so even a short script takes some time.
> If you're feeling daring, and have *backups*, you can try.
>
> At the top of the script is a list of your file stem names. They should
> match the capitalization of your real files because sometimes Windows gets
> confused.
>
> The second list is the list of the directories those respective stems go
> in. There should be a one-to-one correlation. Maybe tomorrow I will learn
> how to split out file name/paths so that two lists are not necessary ;-)
>
> There's a variable that sets how many seconds to wait before checking the
> files again. I have it set to 10 seconds.
>
> To launch, open a powershell, go to the downloads directory used by your
> browser, which should also be where you put the script, and type
> ./launch_all_tw.ps1 <enter>
>
> To launch from a regular batch file would take a magic invocation, so
> that's why I'm starting with the powershell.
>
> I had to add a kludge factor of 1 second to get the datestamp to compare
> correctly. Possibly this would mean that if you did two rapid-fire changes
> in a row, the 2nd one might not be picked up. But I don't know. It might be
> fine.
>
> A script for Linux would be similar, but need completely different code.
>
> -- Mark
>
>
>
>
> # File Stem names. Capitalize per actual file name.
> # Stem must be absolutely unique! Otherwise it might detect wrong file.
> $stemlist = @("notes","Todo")
>
> # List of target directories in same order as stem names
> $dirlist = @("D:\data\Wikis\notes","D:\data\TW2014")
>
> # How many seconds to wait before checking again.
> $waitSeconds = 10
>
> #-- SOURCE DIRECTORY -- NOT USED YET ----------
> $downloaddir = "C:\Users\Mark\Downloads"
>
>
> while(1) {
> for($i=0;$i -lt $stemlist.Length; $i++) {
> $stem = $stemlist[$i]
> $stem
> $dir = $dirlist[$i]
> #$dir
> $copyme = ls $stem*.html | sort LastWriteTime | select -last 1
> $copyme = $copyme.FullName
> #$copyme
> $destination = Get-Item "$dir\$stem.html"
> $source = Get-Item "$copyme"
> #echo Source: $source.LastWriteTime
> #echo Destination: $destination.LastWriteTime
> If($source.LastWriteTime -gt $destination.LastWriteTime.addSeconds(1
> ) ) {
> #echo "Source: " $source.LastWriteTime "greater than "
> $destination.LastWriteTime.addSeconds(1)
> Copy-Item $copyme -Destination "$dir\$stem.html"
> echo "Copying $copyme to $dir\$stem.html"
> } Else {
> echo "Will not be copying"
> }
> }
> echo "Going to sleep..."
> start-sleep -seconds $waitSeconds
> }
>
>
>
>
>
>
> On Monday, May 20, 2019 at 6:05:35 AM UTC-7, @TiddlyTweeter wrote:
>>
>> At the moment, on modern browsers, saving TW without any custom saver,
>> means the save ends up in "Downloads".
>>
>> We have no tool to "auto resurrect" and copy back that save for those
>> kinds of saves. Copying back has to be manual and can get complicated in a
>> forest of downloads.
>>
>> The more I think about this the more odd it seems.
>>
>> I mean, with an "AUTO-RESTORE" from saves in Download to a wiki directory
>> ANY browser could be used and with ANY version of TW. We would not be
>> dependent on specific solutions.
>>
>> Any thoughts on how to do this? And its probable value?
>>
>> I know Mark S. has thought about it.
>>
>> 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 [email protected].
To post to this group, send email to [email protected].
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/513d20c4-2995-4e6d-90f6-7a3793a89bc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
