Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.
Interface:

Graph

...

  • Graph + and - buttons are hiding part of the axis. Move them on the side in google-maps style.

...

  • Add the ability to add thresholding on the plot

...

  • Make the axis labels more readable (done - bigger font)

...

  • Show time units on the graph - the other units just cannot be known by the Robo-Monitor

...

  • (done - X axis is called seconds now)

...

  • Make sure the graph-title is easily readable and NOT confused with axis label (or maybe it should be the Y axis label? )

...

  • (done - y label is now the channel name)

...

  • Axis are limitless so it is possible for the user to get lost ( maybe then the track button can  appear and they can find the plot again )

      ...

        • This is deliberate, and yes they can use the track button. Whenever they are scrolling it is visible. [WONTFIX]
      • The track button may change zoom levels ( in settings )

          ...

            • Low priority
          • Let the user see the numerical value of a datapoint (maybe after they hold their finger on the graph )

          Main Screen

          ...

          • Implement the hierarchical displaying of the data - simplicity and user control

          ...

          • Don't change the

          ...

          • colors when scrolling (

          ...

          • gray to black ). Visual flickr is annoying [FIXED]

          ...

          • Think about sensor names - the screen is small ( maybe break into sub-components )

          ...

          • Make sure that the user can look at only a pre-selected set of channel readings - use e-mail like stars ?

          ...

          • Add configurations settings

          ...

          • Menu - add trace... [FIXED]

          ...

          • Color coding the channels - somehow display freshness of the data.

          ...

          • Create better affordance for scrolling (

          ...

          • shading on the bottom ? )

          ...

          • Add some kind of help, or FAQ with pictures

          ...

          • Freeze functionality so that user can observe and compare values ( maybe a time-slider option in the menu?? )
          Code design:

          ...

          • Refactor plotting to use (x, y) series, not just (y) series over constant interval

          ...

          • Figure out how to jump between activities

          ...

          • Make sure we don't couple the code too tightly to the LCM model - so that it is adaptable to other message passing schemes.
          Backend:

          ...

          • Get dynamic LCM working ( summer )