Seeking YOUR requirement's for extended Import Handling

#21 
<$browse multiple>

Doesn’t seem to work for me on Android, I have to go back and import each file in turn. Might be an android limitation but I was expecting to be able to select multiple files in one go.

Also on my wishlist would be a way to set a repeat file for import. e.g

<$browse pathtofile>

I often need to import the same updated file every time. Probably doable already but I couldn’t find it.

#22

I just tested this on Android 12, from tiddlywiki.com and it seemed to work.

  • The trick seems to be the selection process.
  • I am not sure this is possible with security but I have being trying
  • However if the file is not changing, you just want a fresh copy it is similar to the feature I described as;

Thanks for your feedback

#23

You’re right on the Android thing, it works. I was trying it from within Quinoid, where it must be a quirk, but outside of Quinoid multiple selects work as expected.

The second request is for an ability to always import the same file (an updating json file containing a changing batch of tiddlers). I’m looking for an import button that always selects the same file and goes straight to the import dialogue with it. It sounds like something that’s been done before but maybe not as simple as I imagined.

This doesn’t work, where ‘myimportpath’ is a tiddler with the filepath in it.

<$button>
<$action-sendmessage $message="tm-import-tiddlers" param="myimportpath"/>
Click me!
</$button>

Looking forward to seeing the super importer when it docks. Keep up the great work.

#24

As I understand it, if what you ask could be done, it may be possible for a browser session to access a named file or folder on the local system, this would be a security breach. Perhaps it was possible once or may be possible with local permissions like TiddlyDesktop, twexe or hta files.

#25

Hello TW_Tones,

Perhaps not a direct answer but what I would like from the import process:

  • when I drop another TW on my TW
  • I have the possibility to use it as a plugin library
  • meaning that I onlys see the plugins, themes and language of the dropped wiki with their description and action buttons to install them or update already instaled plugins

Rational: offline use, synchronisation of plugins between different single file wiki.

Best regards,

Eskha

1 Like
#26

Interesting idea. I achive a similar result a different way but will take this into account.

Othe recent discussions How to add a default name/prefix for image drag and dropped into a tiddler in edit mode?

#27

Personally, I would like that when dragging a file into a regular wiki or nodejs version, it would be automatically added to the files folder, and a tiddler with a path field would be created in the wiki where there would be a link to this file of the form files/pic.png. Well, depending on the file extension, you can add a template set by the user in the text field. For example, for pictures <img alt="text" src={{!!files}} width="100" >, and for videos something else. No files should be on the wiki itself, only links to them. When we add files to the wiki itself, it loses its portability. By adding the file to the nodejs version, I can no longer create a single page html version of my wiki. No problem with links.

I would also like to be able to set subdirectories for certain tiddlers. For example, if I drag a file into the Animals tiddler, then let a tiddler be created with a path, Files and Animals tags are added to it, and the file itself is placed in the files/Animals/cat.jpg directory

#28

Welcome @allqu thanks for adding this here however what you are asking for is possible and covered elsewhere. Have a look at discussions with the File Uploads plugin, skinny tiddlers, External Attachments Plugin, _canonical_uri field or Node specific documentation.

  • Perhaps someday we will bring these into the standard import process as you suggest.