<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<div class="moz-cite-prefix">On 2020/05/08 17:42, Dirk Hohndel
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:D1F82D3F-52E5-4331-A34B-7D557D7C7C9C@hohndel.org">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<br class="">
<font class="" color="#5856d6"><span style="caret-color: rgb(88,
86, 214);" class=""></span></font>
<div>So let's go back to what I said earlier about (ab-)using the
filter. How about we use the insanely flexible filter to allow
the user to define their own group:<br class="">
- pick filter settings (dive with tag 'boat', longer than 40min)<br
class="">
- name that 'set' (boat dives > 40min)<br class="">
- pick different filter settings (dive with tag 'boat', 30-39:59
duration)<br class="">
- name that 'set'<br class="">
combine a group of 'sets' into a group which gives you the
slicing of the dives that you want<br class="">
<font class="" color="#5856d6"><span style="caret-color: rgb(88,
86, 214);" class=""><br class="">
</span></font>Now offer those sets as rows in the statistics
table. That way we can reasonably easily allow users to create
almost any statistics they might want.<br class="">
<font class="" color="#5856d6"><span style="caret-color: rgb(88,
86, 214);" class=""><br class="">
</span></font><font class="" color="#5856d6"><span
style="caret-color: rgb(88, 86, 214);" class=""><br class="">
</span></font>/D<br class="">
<font class="" color="#5856d6"><span style="caret-color: rgb(88,
86, 214);" class=""><br class="">
</span></font><font class="" color="#5856d6"><span
style="caret-color: rgb(88, 86, 214);" class=""></span></font></div>
</blockquote>
<p>So what this would amount to are two different initiatives which
could, potentially, run in parallel. <br>
</p>
<p>1) Adapt the existing filter mechanism to store filter 'sets' and
then apply them to the dive list. Mechanisms to store filter
"sets" and combine them to extract dive list information that is
stored in the yearly-statistics table. This table would now have
slightly a different function, i.e. to store the output of the
filter process. It might possibly not be directly displayed any
more but be accessed through the Statistics facility.<br>
</p>
<p>2) Rendering statistics in a panel. For the moment, let us assume
the current (yearly-statistics) table is used to store the results
of the filtering. I cannot see why not since the table is easily
extensible. So this second activity would include reading the
information from the (yearly-statistics) table and presenting it
in the statistics panel. This would be a QML implementation.<br>
</p>
<p>As for activity 1) above, There would need to be some UI
components to manipulate filter 'sets".</p>
<p>A button to add (=store) a set after it has been defined/edited
in the filter panel.</p>
<p>A dropdown box indicating the sets that have been defined. The
sets would probably just be defined as "Filter1", "Filter2", etc.
Clicking on a specific set in the dropdown box allows editing or
deleting a set.</p>
<p>A button to clear all sets. Although the yellow-arrow button to
"Reset filters" could perform this function.</p>
<p>BUT: would this mean that the existing filter panel be rewritten
in QML to be mobile-compatible? For mobile, would this be a scaled
down version or a full-blown version?</p>
<p>Kind regards,</p>
<p>willem</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
</body>
</html>
<br>
<div style="font-family:Arial,Helvetica,sans-serif"><span style="font-size:10.0pt;line-height:105%;font-family:"Segoe UI",sans-serif">This message and attachments are subject to a disclaimer.<br>
Please refer to <a href="http://upnet.up.ac.za/services/it/documentation/docs/004167.pdf" target="_blank">http://upnet.up.ac.za/<wbr>services/it/documentation/<wbr>docs/004167.pdf</a> </span><span style="font-size:10pt;line-height:105%;font-family:Tahoma,sans-serif">for
full details.</span></div>