Hi Everyone, This week I merged the new filter UI code that Berthold has worked on over the past few months. The whole thing really started as part of the discussion of the vision for a new statistics module, and took a life of its own. I am of course totally biased, but I absolutely love the logic, the concepts behind this way of defining filters. And even better, you can save filter sets and reuse them later (they are stored with your git repo). Eventually, they should become available on mobile (if someone does the work that is). And they will be used, as mentioned, as a way to restrict which dives you want to do statistics for.
What would be useful right now is (a) rigorous testing - are there ways to make this fail, to show the wrong dives? (b) more testing - are there things we should be able to filter for (or worse, used to be able to filter for) that aren't supported (yet)? (c) UI improvements (this doesn't mean you need to implement them... just coming up with good ideas how to do this would already be super useful) As for the last point... I am not dissing Berthold's UI work. But he will be the first to tell you that (just like me) he is not a UI designer by trade. So this is super simple, just doing the "default Qt thing". And we get a lot of grumbling from our user base that our UI overall is, err, not so great. A big part of me wants to say "send patches". But I also think it's worth taking this seriously and constantly challenging ourselves to do better. As always, test builds are available in downloads/test on our website and in the -daily repos for Ubuntu, Fedora, openSUSE, etc. Thanks /D _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
