Its brilliant to see Bob being able to actually display external images, 
which node in simple mode doesn't.

I have an issue I'd like to mention. It basically devolves from the 
somewhat circuitous route node takes to storing external files. I found it 
very confusing at first.

Once I set-up "filePathRoot", which is one master directory, I had to 
figure out how, later, when I come to build a single file TW, how I can 
copy over all the files for that particular wiki but for no other.

I came up with the idea of having a two character "shorthand ID" for every 
Wiki which means that later I can copy over all but only the files needed. 
For instance ... in a wiki about "Fireworks" I declare "fw" as the "ID". 
Used like this ... 

[img[./files/*fw*/img/fw1034.jpg]] 

... where filePathRoot is ...
\bag\PortableApps\twBOB\Wikis\ext

... and the physical on-disk file address is actually ...
\bag\PortableApps\twBOB\Wikis\ext\fw\img\fw1034.jpg

Using Windows (at the moment) I copy over all directories and their files 
from "fw" and down into a sub-dir to the output wiki at "/files" (which I 
have to create as its "virtual" inside node). Its a bit weird creating a 
directory you don't need in output, but okay--I would not want to edit the 
TW to adjust for that.

What I am wondering is whether when you create a new Wiki you can define a 
"shorthand ID" for it to ensure you never forget the base address you need 
for files so you don't get in a mess? This comes from concern some of my 
wiki have many images associated with them. 

Or do you have other thoughts on this issue?

Best wishes
Josiah




-- 
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/ed2765c2-3c7c-43bd-9ae3-a23428d43a2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to