Hi Andrew,

The problem is, that — when you merely serve your presentation on localhost 
/ 127.0.0.1 — there is no server at this address to serve files, i.e. any 
"file:///", be it video, images, whatever type of file you want to access, 
it's not accessible using the simple --server command. Even relative paths 
won't resolve and retrieve content, because the server is not (yet) ready 
to handle those requests somewhat "outside" the context of the wiki, i.e. 
your browser requesting a video to render it into the appropriate element.

Here are two possible ways:

1) You can use the --build command to "bake" standalone wikis that you then 
open in the browser for viewing-only. this makes those (relative) paths 
available to the wiki again as we're actually looking at it on the 
"file:///" domain or wherever else you put the whole package deal. So, 
place the videos in an output folder where the built wiki finds them and 
accept for now that while editing they just won't render in the context of 
the --server, so you want to double check your build if it's all properly 
referenced. If you avoid any editing via --server, then you can simply just 
use build so as to verify the output.

3) Another option would be to rely on web-access and to actually put those 
video-data on a webaddress which you then refer to in your tiddlers... 
doing all the talkytalky to download that content whenever the browser 
needs it.

~

I have no idea what it takes to make the tw --server serve files, at least 
in sub-folders of whatever wiki folder / edition is being served.

Best wishes,

— tb

-- 
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 http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2c8ce122-86b2-49a5-a414-f6617310b11d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to