--
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/groups/opt_out.
Thank you
Jeremy, once again thank you for the response but that only answered to the second part of my question. I'm very interested in the first part too, the issue saving the wiki that I describe above.
Thank you
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
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/groups/opt_out.
I think that is not the behavior that I'm getting. I NEVER use firefox or any other browser, I always use tiddlydesktop or node webkit. As you said, I have the "$:/UploadName" set, but it still saving it just locally.
I imagine many users would like to save to both local and cloud locations (with a soft fail for the cloud saver if working offline and the local save succeeded). Why not allow both a local and remote setting, still using priorities within each group, and use either one or both depending on settings? The priorities could even be calculated according to, say, an eval statement if a string is present instead of a number, allowing priorities to change according to current use or environment. (Just a thought :0)
Love what I'm seeing, though I still haven't had a chance to check out the code or use the node server or desktop app.
Cheers, Paul.