User talk:LuitvD

From Openmoko

(Difference between revisions)
Jump to: navigation, search
m
m
Line 2: Line 2:
  
 
== Overview ==
 
== Overview ==
* ''Short summary with list of key features''
+
This panel application will show information on the usage of GPRS, and warn at certain levels
  
 
== Use Cases ==
 
== Use Cases ==
* ''Describe how the user would use this application to get things done. This could be something like "I want to be able to ..."''
+
* I want to know how much MB's of data I used last month.
 +
* I want to be warned if the daily amount of traffic I can use is exceeded
  
 
== Appearance & Interaction  ==
 
== Appearance & Interaction  ==
* ''If there are modes, then Interaction for each mode''
+
The panel application should show data rates over 2 periods of time, ultimately the traffic today, and the traffic in the current billing period
  
 
=== On Tap ===
 
=== On Tap ===
* ''Textual description with a picture''
+
The extra information is shown, containing the following:
* ''Describe how the panel application reacts to tap events''
+
* Traffic today / Average maximum amount of daily traffic
 +
* Traffic this billing period (week/month/year?) / Maximum amount of traffic this billing period
 +
* Number of days from beginning of last billing period / Length of billing period in days
  
 
=== On Tap with Hold ===
 
=== On Tap with Hold ===
* ''Textual description with a picture''
+
A menu with the following:
* ''Describe how the panel application reacts to tap with hold events''
+
* Change billing period information
 
+
* Change display/warning information
== Constraints ==
+
* ''Describes limitations and available of functional aspects''
+
 
+
== Architectural Details ==
+
* ''Items to clear up non-trivial functionality. For instance, diagrams for event / communication flow, data structures, timing details, etc...''
+
 
+
<blockquote>
+
''Use and reference open standards whenever appropriate''
+
</blockquote>
+
 
+
== Implementation Recommendations ==
+
* ''Recommendations on libraries, data structures, etc.. for implementation''
+
 
+
<blockquote>
+
''Use and reference open standards whenever appropriate''
+
</blockquote>
+
 
+
== Unresolved Issues ==
+
* ''List any unresolved issues, topics, functionality, etc...''
+
 
+
== Questions and Answers ==
+
* ''List very common questions with their answers here. Everything else should use the Wiki's discussion feature.''
+
 
+
[[Category:Applications]]
+
[[Category:Panel Applications]]
+
== Overview ==
+
* ''Short summary with list of key features''
+
 
+
== Use Cases ==
+
* ''Describe how the user would use this application to get things done. This could be something like "I want to be able to ..."''
+
 
+
== Appearance & Interaction  ==
+
* ''If there are modes, then Interaction for each mode''
+
 
+
=== On Tap ===
+
* ''Textual description with a picture''
+
* ''Describe how the panel application reacts to tap events''
+
 
+
=== On Tap with Hold ===
+
* ''Textual description with a picture''
+
* ''Describe how the panel application reacts to tap with hold events''
+
  
 
== Constraints ==
 
== Constraints ==

Revision as of 18:11, 23 February 2007

Contents

TESTING, new panel app... possibly

Overview

This panel application will show information on the usage of GPRS, and warn at certain levels

Use Cases

  • I want to know how much MB's of data I used last month.
  • I want to be warned if the daily amount of traffic I can use is exceeded

Appearance & Interaction

The panel application should show data rates over 2 periods of time, ultimately the traffic today, and the traffic in the current billing period

On Tap

The extra information is shown, containing the following:

  • Traffic today / Average maximum amount of daily traffic
  • Traffic this billing period (week/month/year?) / Maximum amount of traffic this billing period
  • Number of days from beginning of last billing period / Length of billing period in days

On Tap with Hold

A menu with the following:

  • Change billing period information
  • Change display/warning information

Constraints

  • Describes limitations and available of functional aspects

Architectural Details

  • Items to clear up non-trivial functionality. For instance, diagrams for event / communication flow, data structures, timing details, etc...
Use and reference open standards whenever appropriate

Implementation Recommendations

  • Recommendations on libraries, data structures, etc.. for implementation
Use and reference open standards whenever appropriate

Unresolved Issues

  • List any unresolved issues, topics, functionality, etc...

Questions and Answers

  • List very common questions with their answers here. Everything else should use the Wiki's discussion feature.
Personal tools

TESTING, new panel app... possibly

Overview

  • Short summary with list of key features

Use Cases

  • Describe how the user would use this application to get things done. This could be something like "I want to be able to ..."

Appearance & Interaction

  • If there are modes, then Interaction for each mode

On Tap

  • Textual description with a picture
  • Describe how the panel application reacts to tap events

On Tap with Hold

  • Textual description with a picture
  • Describe how the panel application reacts to tap with hold events

Constraints

  • Describes limitations and available of functional aspects

Architectural Details

  • Items to clear up non-trivial functionality. For instance, diagrams for event / communication flow, data structures, timing details, etc...
Use and reference open standards whenever appropriate

Implementation Recommendations

  • Recommendations on libraries, data structures, etc.. for implementation
Use and reference open standards whenever appropriate

Unresolved Issues

  • List any unresolved issues, topics, functionality, etc...

Questions and Answers

  • List very common questions with their answers here. Everything else should use the Wiki's discussion feature.

Overview

  • Short summary with list of key features

Use Cases

  • Describe how the user would use this application to get things done. This could be something like "I want to be able to ..."

Appearance & Interaction

  • If there are modes, then Interaction for each mode

On Tap

  • Textual description with a picture
  • Describe how the panel application reacts to tap events

On Tap with Hold

  • Textual description with a picture
  • Describe how the panel application reacts to tap with hold events

Constraints

  • Describes limitations and available of functional aspects

Architectural Details

  • Items to clear up non-trivial functionality. For instance, diagrams for event / communication flow, data structures, timing details, etc...
Use and reference open standards whenever appropriate

Implementation Recommendations

  • Recommendations on libraries, data structures, etc.. for implementation
Use and reference open standards whenever appropriate

Unresolved Issues

  • List any unresolved issues, topics, functionality, etc...

Questions and Answers

  • List very common questions with their answers here. Everything else should use the Wiki's discussion feature.