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 [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/f26fb2d9-0033-43ac-98c0-315edd50ff41%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
