@twMat I think this is a good tip, but suspect it would be best in its own thread on upgrading tiddlyhost wikis and cover the complete process (with a link to/from here). Given my lead post, the only download that occurs is after upgrade, and the download is over the original file. So I don’t think your tip integrates with mine too smoothly.
Not withstanding this above suggestion.
I too find using the chrome bottom bar of download’s, or the FireFox downloads dialogue very useful for dragging files from one place to another or to open a wiki, even across different browsers.
One simple example is download empty, place it in a folder and give it a new name eg mywiki.html then click on the wiki in the bottom bar to open it in the browser and bookmark it. If you have Timimi installed you can go ahead and use the new wiki. Download, Open, Use - too easy.
@Mark_S I would love to make this a generic OS independant instruction if it is possible. I cant see in the top post any mention of;
Perhaps you can clarify?
However perhaps the answer is the Browsers address bar.
The above upgrade approach once the original wiki is open in the browser tab and you confirm you have backups (All of which should be true as a result of everyday use) all operations remain inside the browser so hopefully this makes it valid on all platforms.
The key trick is to use a copy of the full path in the address bar in the clipboard to both provide the;
upgrade file
and save it back to the same path and file after upgrade
Reload the original tab before use to avoid saving the old version.
Of note:
Windows at least allows you to paste a full path and filename into the file open and file save dialogues files name, with ctrl-v or ctrl-insert file. As a result you do not need to look for the file.
The world of Linux is so diverse, it’s possible that someone else somehow has a default file picker that does show a file name box. But mine doesn’t. So it’s not universal on Linux.
In general, these instructions are slowly shaping up to be almost identical to the instructions that are already on TiddlyWiki.com.
Perhaps rather than re-inventing the wheel, developers could make a shell script that uses tiddlywiki on node.js to perform the update. Then you could run it on an entire tree and update all your files at once.
the copy of the path/filename is from the browser address bar
the paste of the path/filename is into the Browsers download dialogue, triggered using the “Upgraders” button Save Upgraded TiddlyWiki file.
With respect I think the above is demonstrably false, one could come across the same method following those instructions, but this method can be much quicker and safer to use.
Given the problem with different dialogues on different Operating systems I think I may have found an even simpler method.
The approach:
A Bookmarklet that drops a tiddler on the original wiki that provides an iframe to the upgrader
Which can access the current path to the wiki (or drop it).
and save the upgraded wiki back to the original filename
This may bypass the need to paste the path into the dialogue.
This does avoid a separate upgrader tab, and forces the upgrader to refresh after use.
The original instructions work everywhere, have only 6 steps, warn you to check your tiddlers, and deal with special case of an encrypted TW. They also give you the address where the upgrade tiddler lives.
The main thing is, with a process this simple, there’s only so many ways of expressing it. You can move around various parts, make other word choices, maybe change one or two things slightly. But it won’t make that much difference.
@Mark_S If you actually follow the tiddlywiki instructions you will find the following;
A range of steps are implied in those instruction’s not given any detail, thats OK you can still do it.
Saving does not address replacement and reload of the file which can result in mistakes.
The upgrade is left un-reloaded in the browser
However my instructions are designed to have the minimum number of steps, and be quickly repeatable, so as to do many upgrades one after the other reliably.
I know it works and is easier than the tiddlywiki.com instructions and reduces risks of possible mistakes because I used it to do a large number of wikis in a matter of minutes.
I love constructive criticism, but please be constructive.
