So you want to distribute the application within the documentation?
If you use eg: github to host 2 different files, you can use a simple download link in TW
and you don't have the mess with converting zip to base64 and back.
Thanks Andreas - So Mario is right with his hint that I need to convert to base 64.
--
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+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
Yes, it is unfortunately it is the only way to do it, without editing core source code.
I btw use powershell with a function I found online[1], that makes it kinda easy to do (since it even copies it to the clipboard).
--
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+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
Wouldn't it be possible to handle all unkown MIME types as binary data ?
That would ensure that people could for example embed word or excel files or a bunch of other file types (at the expense of some txt/ascii based formats). I am not sure if that is a good idea, or if that is possible to implement since most other systems seem to access contentTypeInfo as hashmap.
Wouldn't it be possible to handle all unkown MIME types as binary data ?
That would ensure that people could for example embed word or excel files or a bunch of other file types (at the expense of some txt/ascii based formats). I am not sure if that is a good idea,
Thanks Andreas - So Mario is right with his hint that I need to convert to base 64.