• Members 3 posts
    Dec. 12, 2017, 9:06 p.m.

    I really like this app, but I think one thing that is holding it back from being really useful is the fact that the scales change based on the data range for a given period. I would like to see at least an option for a user to toggle on/off static scales, such that one can relate a certain color to a certain value from day to day and month to month while using this app.

    I don't see this as an extra frill, but basic functionality.

  • Dec. 12, 2017, 9:35 p.m.


    That does exist but is in beta form. You can long-press on the scales and you'll get a dialog to set the range.

    I agree it is a basic functionality and easy to implement but the difficulty is in the design. I'm not sure the current design is right and if I change the design later, it causes angst for users, support emails and sad review. I have learnt it's harder to remove a feature compare to adding it.

    Maybe this is the right time to discuss it.

    Design 0: the current design is that you set the data range for each data for each place. This gives full flexibility but can be cumbersome is you want to set the wave height range for 10 places.

    Design 1: you create a global range setting, just like graphs, then you can set the data for each place to a global range setting. We can have a preset default ranges for each data type so you don't have to assign a range to each data type.

    Design 2: there are preset global default ranges for each data type which you can customise. But you cannot change the range assigned to a place data. I don't think this will work because you may want different temperature ranges for different places.

    Design ?: some combination of the above.

    It is important to get this design right because to change a design (database schema) and migrate data is damn hard and prone to major bugs. I have learnt this the hard way with 4 redesigns of data downloading and 2 database redesigns with a third coming soon.

    I hope you see Flowx, not as lacking basic functionality, but a series of carefully considered designs :-)

    On the note of beta ranges, expect there to be bugs and for the ranges to be lost when I implement the final version.

    Cheers, Duane.

  • Members 3 posts
    Dec. 12, 2017, 9:44 p.m.

    Thanks, Duane. I certainly didn't mean to imply that it's lacking basic functionality, but I wanted to emphasize the importance that I think this functionality could have for some users (and potential users), myself included.

    From your options, I think "Design 1" would make the most sense. Having defaults is a good idea, as I wouldn't want to have to make choices for everything, but leaving the option to manually adjust a range would be nice.

    Thanks for all of your hard work on Flowx!

  • Dec. 12, 2017, 11:45 p.m.

    I didn't think you meant it lacked functionality. I was just expressing my excuse for why it's taking a long time or why I'm slow.

    Yeah, the more I think about it, the more I think it should be like web pages. Separate places and data (HTML) from the presentation (css).

    So we should only have global ranges defined. If you want a different range, you edit or duplicate an existing range and edit it, then apply the new range to the data.

    Here's another good questions, should global ranges apply to both maps and graphs. Graphs require: min (auto or value), max (auto or value), units, scaling (log or linear). Maps additionally require a spectrum. I think we should merge them so we don't need two sets of ranges.

    BTW, read the above as if I'm thinking out aloud.

    Cheers, Duane.

  • Members 3 posts
    Dec. 13, 2017, 1:25 a.m.

    Sounds good. I'd apply global ranges to both, but you're the boss! :)