<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p><font face="Arial">Hi Dirk,</font></p>
<p><font face="Arial">Thanks for your response.</font><br>
</p>
<div class="moz-cite-prefix">Am 14.05.20 um 18:37 schrieb Dirk
Hohndel:<br>
</div>
<blockquote type="cite"
cite="mid:863D0EF4-0591-4D45-8BE9-E03B6CC24102@hohndel.org">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Hi Chrisof<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On May 14, 2020, at 3:30 AM, Christof Arnosti
<<a href="mailto:charno@charno.ch" class=""
moz-do-not-send="true">charno@charno.ch</a>> wrote:</div>
<div class="">
<div class="">
<p class="">Let me give some thoughts from a more-or-less
outsider perspective in this discussion.</p>
<p class="">From a UI-Perspective, I would prefer the
layout to be "Dive List top left", "Filter top right",
"Stats selection bottom left", "Stats display bottom
right". This is with the reasoning that (in the western
world) we work from top left, top right, bottom left,
bottom right, and the logical Workflow would be to have
the dive list as input, which is then filtered, then the
statistics selected and finally the output. This
workflow could also be applied as sort of a wizard for
mobile devices.<br class="">
</p>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>In insulation that may be true. But our existing UI is not
up for discussion. And that very intentionally has the
information that the user interacts with (information tabs and
profile) on top, and the selection of dives on the bottom.
Switching that around to show statistics would lead to a
horrible user experience.</div>
</div>
</blockquote>
I see. Makes sense to be consistent here.<br>
<blockquote type="cite"
cite="mid:863D0EF4-0591-4D45-8BE9-E03B6CC24102@hohndel.org">
<div>
<div><br class="">
</div>
<div>On mobile these would have to be different pages, anyway,
so there the 'layout' question is fairly moot</div>
</div>
</blockquote>
Agree.<br>
<blockquote type="cite"
cite="mid:863D0EF4-0591-4D45-8BE9-E03B6CC24102@hohndel.org">
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">
<p class=""> </p>
<p class="">For selecting the graph type (the bar vs
boxplot discussion): Could this also be implemented as
an option in the "Stats selection" section? I think it's
obvious that some people prefer the more advanced
boxplot version, and some the easier to understand
bar/line graph version.<br class="">
</p>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Every time we opt for "oh, let's make this selectable" we
significantly increase the amount of code that needs to be
written and tested, and we make the UI more complicated by
adding more options.</div>
<div>We already have way, way, way too many options. And we
constantly find that yet some other feature has bit-rotted and
doesn't work anymore. Or that some changes to our code break
something else that doesn't have an active developer anymore.</div>
<div><br class="">
</div>
<div>Today Subsurface is de facto maintained by about five
people, three of which contribute in very narrow slices that
are "theirs", and the other two (Berthold and I) try to keep
everything else working.</div>
</div>
</blockquote>
Makes sense. Bitrot is a pain I just know too good (I'm currently
procastrinating to fix some legacy C++ code on a microcontroller
that won't cooperate with updated host software... The horrors!).<br>
<blockquote type="cite"
cite="mid:863D0EF4-0591-4D45-8BE9-E03B6CC24102@hohndel.org">
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">
<p class=""> </p>
<p class="">Another (third? fourth?) option I just tought
of was a boxplot with included histogram, where the
histogram is displayed as color (instead of a curve). I
have attached an image of a short mockup (Where red
means more, and green means less). I'm not sure if
that's a good idea, but at least it's an idea ;-) <br
class="">
</p>
<p class=""><img alt="" class="" apple-inline="yes"
id="AC15FC72-4497-4476-A71F-70CCCE1AC4EB"
src="cid:part2.2724CCC7.ECC85898@charno.ch"></p>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>It's definitely an idea. It's geeky and cool. I don't think
it will help accessibility (in the sense of being easy to
understand for the casual user).</div>
</div>
</blockquote>
I agree, if there is no selectable graph style this should NOT be
the one.<br>
<blockquote type="cite"
cite="mid:863D0EF4-0591-4D45-8BE9-E03B6CC24102@hohndel.org">
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">
<p class="">About graph orientation: I strongly agree that
the bars (or boxes or whatever) should be vertical, so
that the time-axis (or trip axis or whatever) is the z
axis. </p>
</div>
</div>
</blockquote>
<div><br class="">
</div>
You mean time / categories should be the x axis, correct?</div>
</blockquote>
Yes, exactly. Sorry for confusing X/Z. For me it's just way more
natural to process data from left to right instead of top to bottom,
especially if it's time-based (which I think it will be in the most
cases - categorizing by trips will probably also be sorted by
time?).<br>
<blockquote type="cite"
cite="mid:863D0EF4-0591-4D45-8BE9-E03B6CC24102@hohndel.org">
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">
<p class="">This is (at least for me) the natural way to
read graphs, and also what's currently done in the
dive-display.</p>
</div>
</div>
</blockquote>
<div><br class="">
</div>
Which dive display? The dive list has time as the vertical axis.
Do you mean the dive profile? That's a single dive, not a
collection of dives. Very different.</div>
</blockquote>
Yes, the dive profile. I know it's a different thing, but still it's
a graph and time is on the x axis. I think this would add some
additional confusion if there are differently-oriented graphs.<br>
<blockquote type="cite"
cite="mid:863D0EF4-0591-4D45-8BE9-E03B6CC24102@hohndel.org">
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">
<p class="">And as a last point a proposal for a little
visual gimmick: I would really like to have the
value-axis for depth turned around, so that the 0-point
is on top of the graph (like in the current dive-graph).
With this, the visual representation of the data is the
same as in the physical reality, lower means lower.</p>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Yes, that makes perfect sense for a dive plot (which is why
we do it that way). For statistics I would find it absolutely
painful.</div>
</div>
</blockquote>
I wouldn't ;-) But as said, it's just a gimmick.<br>
<blockquote type="cite"
cite="mid:863D0EF4-0591-4D45-8BE9-E03B6CC24102@hohndel.org">
<div>
<div><br class="">
</div>
</div>
/D
</blockquote>
Best regards<br>
Christof<br>
</body>
</html>