<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px;"><div><div style="font-family: Calibri, sans-serif;">Hi Dirk,</div><div style="font-family: Calibri, sans-serif;"><br></div><div style="font-family: Calibri, sans-serif;">I’ve put some thoughts into this. Not an easy topic as people might have very individual requirements on this topic.</div><div style="font-family: Calibri, sans-serif;">I suggest to take a step-wise approach, determining who would benefit quickly depending on the complexity of the</div><div style="font-family: Calibri, sans-serif;">implementation.</div><div style="font-family: Calibri, sans-serif;"><br></div><div style="font-family: Calibri, sans-serif;">Let me explain my case.</div><ul style="font-family: Calibri, sans-serif;"><li>I love to take films and pictures</li><li>I’d like to assign them to dives</li><li>I’d like to use my mouse to add or delete them (have patches for this already)</li><li>I’d appreciate if the loading doesn’t take too long (no idea on how to do async loading yet with threads but would be interested to dig into)</li><li>I would like to have them stored in a way I can access them from different computers</li><li>I do NOT expect them to load on mobile.</li></ul><div style="font-family: Calibri, sans-serif;">From my perspective, implementing a V1, the easiest is to allow managing pictures “locally” in the way I send a few test</div><div style="font-family: Calibri, sans-serif;">patches already. </div><div style="font-family: Calibri, sans-serif;">I don't know how Google drive or Box work in detail but I know with DropBox I can synchronise my pictures across computers</div><div style="font-family: Calibri, sans-serif;">and even on my iPhone.</div><div style="font-family: Calibri, sans-serif;"><br></div><div style="font-family: Calibri, sans-serif;">If we allow the copy process from the source medial (SD card for example) to a local DropBox location we already have achieved a lot.</div><div style="font-family: Calibri, sans-serif;">I have the patches running with the last master and it works very nicely. Files are copied automatically during the loading,</div><div style="font-family: Calibri, sans-serif;">the new location is stored based on the user preferences. Images that are used in multiple dives are not being physically</div><div style="font-family: Calibri, sans-serif;">deleted on delete. If the preference to manage images is switched off images are not deleted physically either and last</div><div style="font-family: Calibri, sans-serif;">but not least, images are not deleted if the managed location has changed.</div><div><div style="font-family: Calibri, sans-serif;"><font class="Apple-style-span" color="rgb(0, 0, 0)"><font class="Apple-style-span" face="Calibri"><br></font></font></div><div style="font-family: Calibri, sans-serif;"><font class="Apple-style-span" color="rgb(0, 0, 0)"><font class="Apple-style-span" face="Calibri">More comments below</font></font></div><div style="font-family: Calibri, sans-serif;"><font class="Apple-style-span" color="rgb(0, 0, 0)"><font class="Apple-style-span" face="Calibri"><br></font></font></div><div>Guido</div></div></div><div style="font-family: Calibri, sans-serif;"><br></div><span id="OLK_SRC_BODY_SECTION" style="font-family: Calibri, sans-serif;"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> subsurface <<a href="mailto:subsurface-bounces@subsurface-divelog.org">subsurface-bounces@subsurface-divelog.org</a>> on behalf of Dirk Hohndel <<a href="mailto:dirk@hohndel.org">dirk@hohndel.org</a>><br><span style="font-weight:bold">Date: </span> Thursday 22 October 2015 14:08<br><span style="font-weight:bold">To: </span> Subsurface Mailing List <<a href="mailto:subsurface@subsurface-divelog.org">subsurface@subsurface-divelog.org</a>><br><span style="font-weight:bold">Subject: </span> storing pictures<br></div><div><br></div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div><div>So I've been thinking about this for a while and I'm not sure what we do</div><div>right now is the right thing after all.</div><div><br></div><div>So when a user adds pictures to their dive file, the dive file itself</div><div>should contain information how to find the picture and (possibly?) a</div><div>thumbnail of the picture (so if the picture isn't available for whatever</div><div>reason, we can at least show a thumbnail.</div><div><br></div><div>So what does "information how to find the picture" mean?</div><div><br></div><div>- simplest case, it's a file:// url - i.e., where on my local computer</div><div>- of course it has a hash which allows us to find it again if it was moved</div><div><br></div><div>But Subsurface should have a preference option that allows the user to</div><div>specify a network base way to store pictures as well</div></div></div></blockquote></span><div>could be done with radio buttons like O store locally O store remotely (e.g. unc path)</div><span id="OLK_SRC_BODY_SECTION" style="font-family: Calibri, sans-serif;"><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div><div><br></div><div>- cloud storage: pictures are no longer stored as part of the users'</div><div> branch in the git repo - that makes remote operations over super</div><div> slow/bad networks harder and makes the first sync take forever.</div><div> Instead the cloud storage should allow users to upload their pictures</div><div> directly into their picture directory on the cloud server and then to</div><div> download them "on demand" (i.e., if the user clicks on a picture to see</div><div> the full sized version) - but of course look for a local cached copy,</div><div> first. So if I open my repo on my phone it only downloads the picture if</div><div> I tap on it (pictures currently aren't implemented there, anyway).</div></div></div></blockquote></span><div>Can’t comment on this as I am not experienced enough</div><span id="OLK_SRC_BODY_SECTION" style="font-family: Calibri, sans-serif;"><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div><div>- Dropbox / Google drive / other shared storage mechanisma: allow in the</div><div> preferences to tell Subsurface how data can be uploaded / downloaded.</div><div> This can be as easy as a subdirectory of the "magic directory" that is</div><div> used for this cloud data storage. And then use hash-based names to find</div><div> the pictures there.</div></div></div></blockquote></span><div>This is what I played with</div><span id="OLK_SRC_BODY_SECTION" style="font-family: Calibri, sans-serif;"><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div><div><br></div><div>Is this reasonable? What am I missing? I know that Guido has started to</div><div>look into this, as has Robert... please comment / make suggestions how the</div><div>idea can be improved.</div><div><br></div><div>I want pictures to be easy to get to from any device, but I don't want</div><div>them to bloat the git repository as they do today.</div><div><br></div><div>/D</div><div>_______________________________________________</div><div>subsurface mailing list</div><div><a href="mailto:subsurface@subsurface-divelog.org">subsurface@subsurface-divelog.org</a></div><div><a href="http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface">http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface</a></div><div><br></div></div></div></blockquote></span></body></html>