<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 14 Jul 2015, at 22:07, Linus Torvalds <<a href="mailto:torvalds@linux-foundation.org" class="">torvalds@linux-foundation.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">On Tue, Jul 14, 2015 at 12:56 PM, Dirk Hohndel <</span><a href="mailto:dirk@hohndel.org" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">dirk@hohndel.org</a><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">> wrote:</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></blockquote></div></blockquote></div><br class=""><div class="">[lots of things in capital letters]</div><div class=""><br class=""></div><div class="">Gentlemen,</div><div class=""><br class=""></div><div class="">as I said earlier, due to lack of time I did not fully read and understand the previous discussion (in particular the four level indentation list). But please let me add my two cents worth of opinion (at the risk of that it has already been said or worse argued to be wrong).</div><div class=""><br class=""></div><div class="">I would think everybody would agree on the following assumptions:</div><div class=""><br class=""></div><div class="">1) The typical cases should be easy.</div><div class=""><br class=""></div><div class="">2) There should be no surprises to the user (even when they had a different mindset about what the semantics might be or they were using the program/companion app in a way not explicitly prevented by the program).</div><div class=""><br class=""></div><div class="">2a) In particular, the user should not lose data (mainly GPS locations) in an unexpected way.</div><div class=""><br class=""></div><div class="">I would believe this implies:</div><div class=""><br class=""></div><div class="">i) When completing, in the list of possibilities show the taxononomy if available. So it becomes obvious that the user is completing a site and not a name. Don’t offer sites too far away if the current dive has already a location. (The price you have to pay would be that one has to type Blue Hole more than once in a lifetime). If the old dive had a name but no GPS data, do not show a taxonomy and you are in fact just completing a name. Even if the current dive has a GPS fix don’t copy that to the old dives (that should be possible somewhere else but not when adding a new dive).</div><div class=""><br class=""></div><div class="">ii) When entering GPS coordinates or downloading them from the companion, only apply that to the current dive (and again have a different place where the user can chose to copy coordinates from one dive to others, possibly those with the same name or some of those). This complicates later obtaining coordinates for many dives at the same place but again, that should not happen too often. So even when in step i) you autocompleted a site but only meant to complete a name, you can correct that later (e.g. by downloading from the companion) without hurting the data about all the other blue holes (see 2a).</div><div class=""><br class=""></div><div class="">I think we should differentiate between sites and names (a site is a name with a GPS fix) and if we need a site but only have a name make all occurrences of a bare name by default different sites. If the user wants to never the less copy information, that should not be too difficult using the filter and copy&paste.</div><div class=""><br class=""></div><div class="">As I said: Sorry if I only contributed to the noise.</div><div class=""><br class=""></div><div class="">Best</div><div class="">Robert</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>