Riz, I am using FireFox ESR *(Without invoking tiddlyFox on my test wiki)* but Will try the latest FF shortly.
On Windows 10 I just used the MKLINK in a Run as Administrator command Prompt to create a symbolic link where a file stored in the download directory has a symbolic link in another folder. The TW5 can be opened from either location and using the save (download) mechanism, with save set as default for this filetype, you have to indicate the save filename (Folder if you have the setting to allow folder selection) but the default is usually enough, you then have to respond to the overwrite file prompt. Then reloading from either file location the download and the link, will show the updated tiddlywiki. If you have a fixed download folder this should allow you to access your tiddlywiki in any folder but always save/via download to the download folder (The filename is retained) As I have posted previously an "always running batch file" can be used to monitor the download folder and copy updated files to another location if required. You have now made me think what if the batch-file instead updated the symlink? I am thinking each time you save an active batch file or windows service renames the saved file as a new version, updates the symlink on the "symbolic file" (outside the downloads folder) to the new version filename but retaining the original name. Next time you save all you have to do is select save in the dialogue, there is no overwrite prompt as you have removed the original file. I have given the above scenario a test and it works well (manually) Its key advantage is - you can maintain previous versions and simplify the download process. Its disadvantages are - Autosave is not built in or would cause interruptions to your work flow, - We need to develop an easy to use OS Specific Tool The truth is if you just allow FF to select download folders, create a sub-folder in downloads called tiddlywiki and save all your wikis there using symlinks is not much different. Food for thought Tony On Thursday, October 5, 2017 at 5:39:04 AM UTC+11, Riz wrote: > > > > On Wednesday, 4 October 2017 22:34:35 UTC+5:30, Rob Hoelz wrote: >> >> >> >> That being said, I was looking through the Web Extensions APIs, and it >> looks like the downloads API >> <https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/downloads> >> could potentially be used to implement some of TiddlyFox's functionality. >> It means you would need to keep your tiddlywiki.html file under your >> Downloads folder, but it's better than nothing. >> >> -Rob >> > > > This is what I was thinking. Have anyone tried to workaround the > limitation of Downloads folder? As in, via symlinks? What I meant to say > is, if I decide to keep all my TWs in a single folder, and that folder has > a symlink in Downloads folder, can Tiddlyfox continue saving?. It would be > a hack, but it would be better than nothing. > > I have switched my Knowledgebase to TiddlyServer already. However, with > all its benefits, it has some comfortable features missing. For example > with tiddlyfox I can just download an empty wiki, open it and test > something, save it and when done with its use, discard it without a second > thought. With TiddlyServer, I have to ensure I add it to the settings > files, restart the server and finally remove it when done, or restrict > myself to the same path. I hope Arlen would someday look into a feature by > which all files in a particular folder is loaded as standalone TW, so we > can put the empty file in that folder. Until then, I would miss TFox. > > > > > -- 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/8c746a98-0a53-44da-8c67-64e41d9d3d7c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.