#3017 BLOC Trial-3: UI for Measure Activity that has the standard toolbar as UI

[Zarro Boogs per Child]

#3017: UI for Measure Activity that has the standard toolbar as UI
-------------------------------+--------------------------------------------
  Reporter:  arjs              |       Owner:  arjs     
      Type:  enhancement       |      Status:  new      
  Priority:  blocker           |   Milestone:  Trial-3  
 Component:  measure-activity  |     Version:           
Resolution:                    |    Keywords:  ui, icons
  Verified:  0                 |  
-------------------------------+--------------------------------------------

Comment(by AlbertCahalan):

 Replying to [comment:9 Eben]:

 >  4. Bandpass filter (low, med, high).  I think that it's really useful
 to have the slider here (even with only 3 states) because it allows for
 labels at both ends (rather than only one, on a cycling toggle button),
 which provides more meaning about it's function via comparizon.  See how
 this works nicely in contrast to (8).

 There are really two dimensions to this, high pass value and low pass
 value. Maybe just enumerate things as thirds:

 {{{
 a. high freq
 b. high and mid freq
 c. low freq
 d. low and mid freq
 e. everything
 f. mid freq (maybe)
 }}}

 Special treatment for the power line frequency might be needed. That's 50
 Hz or 60 Hz, doubled to 100 Hz or 120 Hz in some circumstances.

 >  5. For lack of a better option, we can use a popup menu to choose the
 interval for now.  1 second should likely be the default, since it
 provides more interesting results when jumping into the software without
 prior knowledge.

 One second between samples, between display pixels, or between grid lines?
 About 2 to 6 seconds across the width of the display seems good.

 >  8. This is the amplitude slider.  I like this idea a lot, and adding
 the labels at both ends makes it clearer still.

 This is taking lots of space that could go to the graph. Automatic range
 adjustment could reduce the need for the slider. (can't entirely eliminate
 it though)

 >  9. Details.  These are toggled from (14).  They are aligned on the ":"
 character.

 Drawing horizontal lines for the RMS and average values would be nice. The
 numeric values could be displayed on the lines.

 >  10. This is the graph region.  I think a subtle grid like that shown
 would be nice, and increasing the weight of the line itself would really
 go a long way to improving the visual of the waveform.

 Making this bigger would be good. Reducing the other stuff on the screen
 would help. There could be a way to make the graph full-screen.

 An option for a logrithmic vertical scale would be good.

 >  12. This area at the left, free of controls, can become a history of
 logs within the Measure session.  Clicking on a log directly will switch
 to log mode and show its corresponding graph.  Clicking play again would
 return to live mode.

 This is taking up lots of space that could go to the graph.

 For the older/smarter kids, consider adding:

 {{{
 a. X-Y graphing support
 b. trigger ability
 c. waterfall plot / spectrogram / spectrograph
 d. alternate input: microphone, CSV file, mesh traffic, drawn line, etc.
 e. alternate timing: keypress, other channel, etc.
 }}}

 BTW, with a waterfall plot / spectrogram / spectrograph display, be sure
 to watch out for display gamma. You have to convert to sRGB after making
 the linear/logrithmic choice. Settings include window size, window
 overlap, frequency scale linear/logrithmic, intensity linear/logrithmic,
 and frequency range.

-- 
Ticket URL: <https://dev.laptop.org/ticket/3017#comment:10>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system