Measure/Plans: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Measure Activity future plans and design discussions)
 
(cat)
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
''Plan of release versions. Pulling together many features that have been experimented as various forks, into a sequential set of releases with feedback from each release affecting features for next release.''
=For version 17=


=For version 18=



==Plans==
==Plans==
# CSV logging support and making an explicit entry in journal for each CSV file created
<pre>
# Measure toolbar split into Sound and Sensors toolbars -- Within the sensors toolbar there would be two buttons which allow one to select amongst time and frequency base. There would be a slider also that allows one to change the time scale.
1. CSV logging support and making an explicit entry in journal for each CSV file created
# A text box in the bottom that remains in the Sound as well as Sensors mode, and allows one to see details about the signal.
2. Measure toolbar split into Sound and Sensors toolbars
# In the sensors context, there would not be any slider bar. The text box at the bottom will show details about the signal as well as actual sample values ( -32768 to +32768 )
3. A record/logging button at the bottom
4. A text box at the bottom that shows details. RMS , AVG, PK-PK, X Axis Scale and Y Axis Scale
# A record/logging button at the bottom. The basic icon should be similar to that used in Record Activity.
# On both the sensor and sound contexts there is an icon with the XO colors that shows where the input is. Within sensors it would point to the MicIn jack and within sound it would point to the built in microphone
5. Context switch between Sound and Sensors changes the electrical settings

6. On both the sensor and sound contexts there is an icon with the XO colors that shows where the input is. Within sensors it would point to the MicIn jack and within sound it would point to the built in microphone
</pre>


==Rationale==
==Rationale==
# Spreadsheet Activity would be able to read the CSV file generated and show a variety of graphs based on the data
<pre>
# Bias and AC/DC are complex terms for understanding. Sound and sensors are two categories based on the contextual use.
1.
# One should be able to measure whatever one is doing.
</pre>
# For other sensors later, there is a need for showing numbers and values and it doesn't make sense to show them on the drawing area
# Like how it is done within the Record Activity
# To help the user to identify what the source is. It is hard to guess that Mic In is the place where one needs to connect the sensors
# There is no need for a amplitude slider in DC mode

=For version 19=
# Internal temperature sensor
# Battery and charge display
# Camera RGB values
# Waveform is the XO color (taken from sugar profile)


=Design specifications for Measure Gen2=
=Design specifications for Measure Gen2=


[[Category:Measure]]

Latest revision as of 03:13, 12 May 2008

Plan of release versions. Pulling together many features that have been experimented as various forks, into a sequential set of releases with feedback from each release affecting features for next release.


For version 18

Plans

  1. CSV logging support and making an explicit entry in journal for each CSV file created
  2. Measure toolbar split into Sound and Sensors toolbars -- Within the sensors toolbar there would be two buttons which allow one to select amongst time and frequency base. There would be a slider also that allows one to change the time scale.
  3. A text box in the bottom that remains in the Sound as well as Sensors mode, and allows one to see details about the signal.
  4. In the sensors context, there would not be any slider bar. The text box at the bottom will show details about the signal as well as actual sample values ( -32768 to +32768 )
  5. A record/logging button at the bottom. The basic icon should be similar to that used in Record Activity.
  6. On both the sensor and sound contexts there is an icon with the XO colors that shows where the input is. Within sensors it would point to the MicIn jack and within sound it would point to the built in microphone


Rationale

  1. Spreadsheet Activity would be able to read the CSV file generated and show a variety of graphs based on the data
  2. Bias and AC/DC are complex terms for understanding. Sound and sensors are two categories based on the contextual use.
  3. One should be able to measure whatever one is doing.
  4. For other sensors later, there is a need for showing numbers and values and it doesn't make sense to show them on the drawing area
  5. Like how it is done within the Record Activity
  6. To help the user to identify what the source is. It is hard to guess that Mic In is the place where one needs to connect the sensors
  7. There is no need for a amplitude slider in DC mode

For version 19

  1. Internal temperature sensor
  2. Battery and charge display
  3. Camera RGB values
  4. Waveform is the XO color (taken from sugar profile)

Design specifications for Measure Gen2