I've wanted drag-n-drop to create an image link for the longest time. But 
we're told that the browser security won't let tiddlywiki "see" the 
original file path. This seems odd, since the browser can "see" all the 
data that gets dropped on it and even create the image. It can also "see" 
and portray any image file on the file system. It can even browse anywhere 
in the file system. So why is it so protective about the file path? It 
reminds me of that scene in Airplane II where the terrorist with a bazooka 
is allowed through the check point but a little old lady with a bobby pin 
gets jumped by a dozen guards. 

You can use tiddlyclip in local mode to import image paths from a nearby 
tab that browses local files, but this is a bit fiddly requiring you to set 
the docking TW (which is forgotten every time your browser reboots), set 
the local mode, open a tab for file browsing, and then use the designated 
clip. 

About keyboards: OTG cables do not work with all android tablets and 
devices. Generally they work with the name-brand models, but not always.

There's a "hacker's" software keyboard that makes it easier to select text 
and use commands like shift-select and  Ctl-C/V to copy and paste. This is 
often more reliable than the default long press method. 

At this point, on the tablet, I've surrendered the notion of being able to 
capture information into TW. I use Evernote or Simplenote for capture and 
then later, on the desktop, move the information into TW. Real apps are 
much faster for entering and editing information on the tablet. But I get 
pretty good performance out of using AndTidWiki to read articles I've 
previously captured in a 6Mb TW5 file.

I can imagine an Android utility that would watch a designated file 
directory, and then create a tw data json file that  contains the image 
link in a separate directory. You would need to manually import the JSON 
file, but this would save you having to hand-craft the links. 

Mark

On Tuesday, March 15, 2016 at 5:02:13 AM UTC-7, HC Haase wrote:
>
> I agree on what have already been said. TW is amassing in so many ways but 
> has some pitfalls.
>
> a. if you want to keep the size of the wiki down you need to keep photos 
> external and it is clumsy to write links.
>
> b. It takes to much time to give photos there own tiddler and the 
> transclude them.
>
> solutions proposals
>
> it would be great if you cold drag“n drop photos into the text editor of a 
> tiddler and then either include it as a link to a image tiddler or a link 
> to the external photo (e.g. with a save dialog), in that place in the text.
>
>
>

-- 
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4626dc6d-e718-4135-b261-88c1ff1c98f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to