You are working in the Edge browser and only Download Saving is possible.
CAN you, within the TW running in Edge, define a sub-directory of the Downloads Folder that download saves would go to?
I'm asking this here first.BackgroundYou are working in the Edge browser and only Download Saving is possible.
IssueCAN you, within the TW running in Edge, define a sub-directory of the Downloads Folder that download saves would go to?
I see that PMario did it for a plugin.
Would it be possible in a TW in browsers that don't support such plugins? I.e. that TW itself specify that Download go to a SUB-address of whatever the browser determines is downloads?
As you say I would think it possible because the backups plugin (even the save) does this.
One could possibly do it to other locations except the browser does not have the rights. In a related need I would love to be able to hard code export of other newly created or overwriting files to a known location, still needing user intervention but such that the user need not "hunt and peck" or remember where it is they want to save each time.
to ...<$action-sendmessage $message="tm-download-file" $param="$:/core/save/all" filename="index.html"/>
<$action-sendmessage $message="tm-download-file" $param="$:/core/save/all" filename="wiki/index.html"/>
Part of my interest in this is in relation to "Polly", but also simply leveraging "Downloads" folder to be more useful when you don't have an available plugin for TW.
I find it, still, not good that TW's often have to be in the "Downloads" folder at all. But if they have to be, then far better in a sub-dir.
Some users, like me, download vast numbers of things daily and having to store TW in the midst of that is not ideal.It is also counter-intuitive.
I'm planning to release a file-backups version for Chromium based Edge. ...
The low level, web-extension APIs should be compatible between browsers. ... BUT they are not.
My ff and chrome are set to allow me to save downloads anywhere. So it is possible to go to a folder and save over a previous download. Since we can set the save filename in a wiki we can always download with a preconfigured name but we need to remember the folder. If the save mechanisium were fed the local path and opened the save/download dialogue in that folder using the default download would be smoother but I am not sure if this is possible.
I wonder if we had a tiddly wiki mime type if we could add different handling within the browser for tiddlywiki files as microsoft, pdf viewers and others already do. All browsers should allow this mechanisium.
You can associate an application to handle different mime or document types, perhaps we could have one that trapped the download and ensured it was deposited inn the right folder, backup original file and saved with the original filename.
The above could make the default save less dependant on user interaction.
Just some speculation based on observations with other files in browsers especialy within the office cloud integrations with local apps and folders. They can do it so surely we can?
regards
Tony
... If the save mechanisium were fed the local path and opened the save/download dialogue in that folder using the default download would be smoother but I am not sure if this is possible.