On Sat, 25 May 2013, Eric Shulman wrote:
Thanks for the quick response.
saveChanges() calls on saveMain() which, in turn, calls on
fileSave(). fileSave() uses a 'fallack cascade' to attempt to save
the file using various forms of browser-specific *local file I/O* (moz/
TiddlyFox, webkit/TiddlySaver, IE/ActiveX). In previous releases, if
these methods fail, the "save changes" fails as well. However, in
TW280, rather than failing, fileSave() calls on
HTML5DownloadFileSave() to construct a link element ("A") with the
file contents encoded as an href="data://..." URI and then
automatically clicks the link to initiate a "download" of the data://
URI as an alternative method of saving the file via the browser's
standard download dialogs.
Given the stack of options for saving, why is the
HTML5DownloadFileSave last? What I mean is, what is the disadvantage
compared to the others?
Should it perhaps be first?
In any case, this could very well be quite interesting for tiddlyspace
stuff. I'll try to get the beta version onto tiddlyspace soon so
people who are more tiddlywiki savvy can have a play.
--
Chris Dent http://burningchrome.com/
[...]
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
