Hi Paul > > 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) >
I was thinking that it might be useful to be able to specify an explicit saver for a save operation, with the priority-based cascade just occurring if no saver is specified. It might also be helpful if savers could dynamically choose their priority based on environmental factors (eg http:// vs. file://) > 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. > Great, hope you enjoy it when you get a chance, Best wishes Jeremy > > Cheers, Paul. > > -- Jeremy Ruston mailto:[email protected] -- 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. For more options, visit https://groups.google.com/groups/opt_out.
