Jed, I understand that limitation, but once we have "manually" provided those folders we should be able to browse them and select images and use our own code to add a field containing the source folder.
I put quotes around "manually" because getting all folder names is like this in the windows commend prompt "dir /s /ad /b >result.txt" and I am sure similar on linux. Although we may restrict this to our images/pictures folders and subfolders in the image case. Regards Tony On Tuesday, August 7, 2018 at 6:22:02 PM UTC+10, Jed Carty wrote: > > Tony, > > The browser can know whatever you tell it yes, but when you drag and drop > a file into the browser or import it another way the browser only gets the > file name, not the path. You can give the browser the path if you want, but > you have to do it manually that is how _canonical_uri fields work. So you > can list all the folders you want in tiddlywiki, but it doesn't have a way > to automatically associate a folder with an imported file. > > And if you are going to talk about 'rights' of the browser vs the person > using the browser in this context, the adversarial model used by browsers > has a lot of problems, not as many as that of phone OS's, but there are > plenty of problems. DRM and adtech are two big reasons but that is > something that I shouldn't rant about here. > -- 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/461eeb8f-f4fb-47b9-be20-9b8c3d2e4425%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
