Seems a bit specific to your use case and out if the realm of a web based 
application. Although admittedly I do not fully understand what you are 
requesting.

On Thursday, November 6, 2014 8:43:37 PM UTC-5, infernoape wrote:
>
>
> I'm wishin, that like the operating system creates shortcuts, draggin the 
> favicon from the address bar into an open tiddler would create a tiddler 
> with the address in the _canonical_uri field, title in my subtitle field 
> and content field, and zTXt chunk the contents of any text from the page 
> and tag it with the name of the tiddler that I dragged it into. Maybe that 
> could be a really cool pluggin.
>
>
>
> Sent from my Samsung Epicâ„¢ 4G Touch
>
> Blake Blacksmith <blakebl...@gmail.com <javascript:>> wrote:
>  
>
> Sorry if I was unclear but I do not support the idea of importing files 
> directly into an html file such as TiddlyWiki since this will cause slow 
> down and a loss of file mobility. My request for a link import was based on 
> linking to relative files and folders.
>
> One point to note is that you'll get different behaviour if you drag the 
>> link into the text editor within a tiddler you are editing ... We could 
>> indeed tweak it to be a relative link if possible.
>
>
> I think this would vastly improve the process of including files in TW.
>
> By the way, when I drag a file into the text region of a Tiddler during 
> editing I get redirected by my browser to the file (using most recent 
> Chrome on Win 8) so I do not get the absolute link you mentioned.
>
> -Blake 
>
>
> On Thu, Nov 6, 2014 at 4:46 PM, Jeremy Ruston <jeremy...@gmail.com 
> <javascript:>> wrote:
>
>> Hi Blake
>>
>> One point to note is that you'll get different behaviour if you drag the 
>> link into the text editor within a tiddler you are editing. By default, 
>> you'll get the absolute link. We could indeed tweak it to be a relative 
>> link if possible.
>>
>> The behaviour I was thinking about in my answers above is when you drag 
>> the link into the rest of the TiddlyWiki window, which triggers the import 
>> mechanism. It's still unclear to me what we should do when we try to import 
>> a link.
>>
>> Best wishes
>>
>> Jeremy.
>>
>>
>>
>>
>> On Thu, Nov 6, 2014 at 9:36 PM, Blake Blacksmith <blakebl...@gmail.com 
>> <javascript:>> wrote:
>>
>>> We could indeed introduce special behaviour for dragging links; the 
>>>> browser identifies the text as a link when it is dropped. *The problem 
>>>> is that it's not clear what that behaviour should be; for image links*, 
>>>> ...
>>>>
>>>>
>>> I do not think the job of a drag-and-drop file-link *inserter *should 
>>> include determining what type of data the file-link leads to. That should 
>>> be up to the user to decide with [img[...]] or other user-defined file 
>>> handling macros.
>>>
>>> The most general & simple solution would be that the drag-and-dropped 
>>> function should:
>>>
>>> 1. grab the absolute-file-link string file
>>>
>>>    - such as: *file:///d:/data/Proj/*
>>>    *PhotoScrapbook/origs/%7B040%7DIM-3837.jpg*
>>>
>>>
>>> 2. check that the file is within the TiddlyWiki's folder 
>>>
>>>    - for example: *d:/data/Proj/**PhotoScrapbook/ *
>>>    
>>>
>>> 3. paste the appropriate link into a text box
>>>
>>>    - if it is in under same folder as the TiddlyWiki then paste the 
>>> *relative 
>>>    *file link text : *file:.//**origs/%7B040%*7DIM-3837.jpg
>>>    - and if the file is not under that folder assume the user wants the 
>>>    file to be imported into the TiddlyWiki are raw text.
>>>
>>>
>>>    - could also have the option to paste the *absolute *path link text 
>>>    : f*ile:///d:/data/Proj/*PhotoScrapbook/origs/%7B040%*7DIM-3837.jpg 
>>> *(although 
>>>    I am not sure under what scenario this would be useful).
>>>
>>> How does that sound? Is that doable or does that violate some browser 
>>> security limitations?
>>>
>>> Blake
>>>
>>> -- 
>>> 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+...@googlegroups.com <javascript:>.
>>> To post to this group, send email to tiddl...@googlegroups.com 
>>> <javascript:>.
>>> Visit this group at http://groups.google.com/group/tiddlywiki.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Jeremy Ruston
>> mailto:jeremy...@gmail.com <javascript:>
>>  
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/k-cMEGkOV-8/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com <javascript:>.
>> To post to this group, send email to tiddl...@googlegroups.com 
>> <javascript:>.
>> Visit this group at http://groups.google.com/group/tiddlywiki.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  -- 
> 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+...@googlegroups.com <javascript:>.
> To post to this group, send email to tiddl...@googlegroups.com 
> <javascript:>.
> Visit this group at http://groups.google.com/group/tiddlywiki.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Reply via email to