The main advantage, and it's kind of weak, is that if you use the image in multiple places, but then need to change the directory, you will only have to change the one canonical URI address.
It's weak, because you can do much more with macros. With a macro and a configuration tiddler, you can change your image path depending on your platform. This is useful if you can't use a relative path on some platform. For instance, on Android you might need your TW to be in downloads directory for saving on an internal drive with limited space, but all your images are off on a sdcard where there is more space. Likewise, switching between Linux and Windows where the file pathing is completely different. The problem with macros is that they're not part of the standard core, and you'd have to rewrite all your image links like <<img "MyFavoriteFossaImage.jpg">>. It would be great if all internal image links referenced a base image path configuration tiddler. Then you wouldn't have to use a macro to display images in a flexible manner. I suppose that would be a fun parser rework project. -- Mark On Thursday, May 24, 2018 at 3:10:26 AM UTC-7, Ste Wilson wrote: > > Cheers Mark S for the explanation :D > > So... I've been embedding external images with > [img[http://url.svg]] > > But I could do this with canons and uri? > > What are the advantages as, having had a look at the documentation, I'm > still not massively clear... > > -- 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/9ac89691-efc6-43a7-826a-7b26e252b764%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
