User talk:LuitvD

From Openmoko

(Difference between revisions)
Jump to: navigation, search
m
m
Line 1: Line 1:
= TESTING =
+
= TESTING, new panel app... possibly =
  
 
== Overview ==
 
== Overview ==

Revision as of 17:47, 23 February 2007

Contents

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.
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.