Hi Rick,
without having the evidence in code to support my claims, from memory, I
recall that the process should work like this:
1) Tiddlywiki renders a tiddler called $:/core/save/all (or similiar)
internally and hands off the result to a saver module (not syncer)
2) The saver module is specially selected depending on the situation,
but for the normal browser-save option is either called "manualdownload"
or just "download"
3) Basically what the download saver-module does is get the rendered
version of a tiddler in a form that fits the data contained (either text
or binary)
4) And it then injects a link into the DOM containing a data-url which
contains all the data that is supposed to be saved and clicks that link
(and then removes it from the DOM)
Depending on the situation, it might employ more sophisticated things
(like the browser's API if existent) to influence the filename for example.
Don't nail me on the specifics, but that should be the general process.
(I am afraid that I don't have the time to actually dig in TW's code
right now, but I can take a look and figure out the details more clearly
later)
Hope this was of some help.
/Andreas
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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/tiddlywikidev.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/555F99F2.8000506%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.
