Re: [tw] Re: Blog capabilities of TiddlyWiki

2017-08-13 Thread TonyM
Eric, Yes Understood. Nicely put. But I sill see the following workflow possible, - Create Images folder below Tiddly wiki - Drag and Drop images to tiddly wiki - Check Import as external files/Or Reference - Enter the relative or absolute path (do the Job the browser will not) -

Re: [tw] Re: Blog capabilities of TiddlyWiki

2017-08-13 Thread 'Mark S.' via TiddlyWiki
But ... as I asked earlier. Is this true if dragging and dropping from an external web site? I suspect not, since knowing the url to a web site is what browsers do all the time. So, it should be possible to drag and drop and then construct a tiddler based on the file type and file name. AND, if

Re: [tw] Re: Blog capabilities of TiddlyWiki

2017-08-13 Thread Eric Shulman
On Sunday, August 13, 2017 at 6:31:13 PM UTC-7, TonyM wrote: > > Another thought is the import feature, permitting import of external links > to selected files, and allow a multi-select, I would have thought the > browser has to know the full path to do this import?, but I expect I may be > wron

Re: [tw] Re: Blog capabilities of TiddlyWiki

2017-08-13 Thread TonyM
Jeremy That explains the mysterious omission of such a feature. A key use case for me is when I have a folder of images and PDF's I want to display in a tiddlywiki yet I want to avoid loading the tiddly wiki up and making it too big. If I could choose a specific library ..\images Place my files

Re: [tw] Re: Blog capabilities of TiddlyWiki

2017-08-12 Thread 'Mark S.' via TiddlyWiki
What I do is have a variation of Tobias ximg macros. I have a drop-down list that let's me set the base path of all the macros depending on platform. In addition, if a tiddler is tagged with D:2017, then the sub-path of the path name will be /2017. This will allow me eventually to archive or h

Re: [tw] Re: Blog capabilities of TiddlyWiki

2017-08-12 Thread @TiddlyTweeter
OBSERVATION 1 -- *Easier translation/conversion to portability*--of absolute paths to relative--could be a godsend for TW. For at least 2 reasons. First, universalism of platform (offline / online). Second, emerging issue if you want to go httpS: ... relative paths don't throw an issue on that

Re: [tw] Re: Blog capabilities of TiddlyWiki

2017-08-12 Thread 'Mark S.' via TiddlyWiki
But what if the dropped link was from an external web source? Does the browser still hide the address? Shouldn't it be able to access that url? And if the base url was the same for your TW and the dropped object, wouldn't it be possible to construct the relative path ? I'm thinking that in the

Re: [tw] Re: Blog capabilities of TiddlyWiki

2017-08-12 Thread Jeremy Ruston
Hi Tony > Drag and Drop but only create external links? Allowing a relative link such > as .\images would allow the tiddlywiki to be moved with its media to a host. That trouble is that browsers do not reveal to JS code the original path of the dragged file. We only get the file name portion. B