Jeremy Ruston wrote:
>
>
> Does anyone know if it is reasonable to request that DnD from an OS window 
> into an editor should give a list of file paths? Or is there some "obvious" 
> reason why this doesn't already work? Is it purely a browser issue? Or 
> maybe it *does* work in other OS'es than Windows?
>
>
> This comes up surprisingly frequently.
>

I assume that's because it is still somewhat iffy to work with images in 
TW, both to import or to draw them.

 

> When dragging and dropping, browsers do not expose the original file 
> location; JS code just sees the filename and content.
>

OK, but neither DnD'ing a single file nor multiple files into an editor(!) 
yields anything (except space characters). If it worked, it would be simple 
to add a path to them, or use a default path to some default folder so 
_canonical_uri tids could easily be created via DnD. This can be contrasted 
with an image on a webpage where its url can be directly DnD'd into the 
editor to get an url string there. (It also works to DnD one file, 
including full path, from "file:///C:/Users/....")


TiddlyDesktop supports the external attachments plugin which does what you 
> want: on TiddlyDesktop we have access to the file path and so can create 
> _canonical_uri tiddlers to point to imported tiddlers. You can install the 
> plugin from the official plugin library.
>

That'd be for @Bruno who posted the OP. (Personally, I mostly use 
TiddlySpot for the majority of my wikis so I can't use local filepaths 
anyway - but it would be neat if it were possible to pull in an image link, 
e.g http:....jpg and it was recognized so the created tiddler was a 
_canonical_uri with the url.... but this is another question.)
 
<:-)

-- 
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/d534d6c7-4aef-43fa-9d71-2ce11975f7a5%40googlegroups.com.

Reply via email to