diff options
author | Dirk Hohndel <dirk@hohndel.org> | 2016-01-10 21:40:03 -0800 |
---|---|---|
committer | Dirk Hohndel <dirk@hohndel.org> | 2016-01-10 21:40:03 -0800 |
commit | a27d78af03d3b622b32b3347daf7e727708b9f40 (patch) | |
tree | c0d2b104e075029e86d92a46f79a59bf576c6e1e /export-html.cpp | |
parent | 60d546331180df1b5cad61ce1646afdfb2ef522f (diff) | |
download | subsurface-a27d78af03d3b622b32b3347daf7e727708b9f40.tar.gz |
Save a dive has to mean "save to local storage" on mobile
While it makes sense to have the concept of "what's in memory" and "what's on
disk" in a desktop application, on a mobile device that seems like the wrong
approach. If the user edits a dive and taps on "save", they reasonably expect
this to be saved to storage (so our local cache of the remote git repository).
And "Upload to cloud" then pushes the data to the cloud server. It may even be
reasonable to do that automagically, but that I'm not so sure about.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'export-html.cpp')
0 files changed, 0 insertions, 0 deletions