Thanks PMario & Mark S. Very useful thread for me. Very clarifying.
Mark S. > I too am puzzled why you would need/want the TW file to be nearly empty. >> > PMario... > I think, that's obvious. All the image related data can be stored and > distributed with the image. TiddlyWiki is "just" the app, that lets you > have a nice presentation of this data. ... I do like the idea. > I do think there is merit is using TW as a minimalist "shell" for some uses. I think this is an example where it could be appropriate. My starting idea was that I want the image meta-data handing to be done dynamically via a plugin. Partly this was, as PMario, you understood, so I can concentrate in the TW on getting the visual presentation right. It really is not necessary that you have 4,000 individual tiddlers. What could be good is when a specific dynamically shown image is interesting you can favourite it and in that case create a tiddler for it. My main technical issue is I can't program Javascript. I maybe could work out, with a bit of help, porting some JS based EXIF extractor IF I knew it were not in conflict with TW's way of working. There are several. I look at them a bit more and see where I get. Where I am: Two possible routes: minimal image data extracted to TW; or, plugin based dynamic EXIF extraction. Both look workable. Thanks Josiah On Thursday, 18 October 2018 12:10:01 UTC+2, PMario wrote: > > On Thursday, October 18, 2018 at 4:52:12 AM UTC+2, Mark S. wrote: >> >> Sure enough, you can find one with the first google search (called, >> surprisingly, EXIF.js). >> > > IMO exif.js contains all the functionality, that is needed to extract the > different values. > > One problem I see is, that the value description is hard-coded english > language. For a TW plugin, we would want that to be translatable. > > >> But it wants as input an image element from the DOM. Can you get that in >> TW ? >> > > That's a point. Especially, since TW uses the DOM src-element if an image > is imported with _cannonical_uri. .. This means: all the work is done by > the browser, when it shows the image. TW does almost nothing with the image > data. ... So we would need a way, to extract the exif data, after the > browser did load / show the image. > > >> I too am puzzled why you would need/want the TW file to be nearly empty. >> > > I think, that's obvious. All the image related data can be stored and > distributed with the image. TiddlyWiki is "just" the app, that lets you > have a nice presentation of this data. ... I do like the idea. > > > >> The information is not going to be searchable , if that is a goal, unless >> it is loaded in the TW. >> > > That's right. > > -m > -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/dd9747c6-a612-4051-8781-b7a56686be70%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
