Folks,
*Background* If you supply a filename to the export process it will use that filename to save the file, eg JSON file. If you add a path into the filename given to the export/save file C:\Data\TW5\TW5 Intranet\MyBundles\Working\myfile This get's sanitised? to C__Data_TW5_TW5 Intranet_MyBundles_Working_myfile.json You must respond to the save dialogue, so export can not occur to a local folder unless a user intervention occurs. If however when the save dialogue appears you paste the foldername in front of the filename you can save to the desired location, however this is fiddly and demands forethought and multiple steps. *The Question* Is it possible to allow the full path and filename to be passed to the save file dialogue, such that if known, the path will be used to save the file? Perhaps the import process as well? *Why?* - This would allow known folders to be recorded in tiddlywiki for known folder/files and allow this information to be used to simplify export/saving to various locations. - It would allow a default file location to be set for saving exported files and perhaps even wikis (If the browser permits selecting the location only) - We could encourage in a LAN environment that exported files saved wikis, are saved in a known location unless changed. - We may be able to do the same for the import function so we could import from our local tiddlywiki tools folder without having to search or select the folder. *Finer details* - Even TiddlyDesktop, that has access to the local file system, the export still sanitises the name as above, surely we can override this limitation there, if no where else? - I am aware of apps such as the Office 365 Suite that can save to and remember where the file was when opened in the browser, so it is possible. - The same would be good for URL's of a server able to receive the exported file and save it, or to access an online "library of files", if the import and export allowed an address to be given - It is fine for the interactive open or save dialogue to intervene forcing a conscious selection by the user to reduce the security risk, the save mechanisium will only work if the browser permits save to any location (Not only downloads). - You can only save to where the interactive user has rights to save, I believe windows, for one, may resist saving to the system folder unless overridden. This may require a PR but I am asking here first in case someone has an answer. Regards TW Tones -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7b0ab1c7-e0ed-4ab1-9dec-34649a211373o%40googlegroups.com.
