Screen Saver
From Openmoko
Contents |
Overview
This article defines the Screen Saver Applications Application, an application designed for the OpenMoko platform. This is a Native Finger-Based application.
The LCD on the neo cannot be viewed without the backlight on.
There is a trade off between how bright it appears with a given backlight, and viewing without the backlight, and the designers have picked the former. Viewing the screensaver needs the backlight on, which uses lots of battery power.
Use Cases
Here are some possible use cases:
- I want to be able to quickly view the current time and date
- I want to be able to see and check my missed calls
- I want to be able to see and check my messages
- I want to be able to see and check my calendar event notifications
- I want to be able to see the current Profile
Many of these seem to be in the Today application.
Layout Components
Application Area
Key Features:
- Display current time & date
- Display number of missed calls
- Display number of missed messages
- Display number of calendar event notifications
- Display the current profile
| 15:46:37 | ||
|---|---|---|
| Fri May 18 | ||
| silent mode | ||
| 3# | 99@ | * |
With # being a call icon (text balloon?), @ being a message icon (envelope?) and * being a calender event notification icon (clock dial?). Of course the time and date will be in the format as specified by the user system preferences. Note that visually the first and last line is the most easy to read, hence the most volatile information is positioned there.
Note that in case of a single calender event notifcation, the 1 is not displayed. Only above 1 the number is displayed with a maximum up to 99, indicating 99 or more.
Footer Area
This application is full screen and therefore has no footer information
Saving the screen
To actually save the screen from burning in, all that s displayed in full screen mode needs to move around. Initially and after each x seconds, the bounding box of all the information which is being displayed on the screen needs to be repositioned at a random location within the full screen. To make this repositioning easy on the eyes, it should fade away and fade back in the new position.
Constraints
(TBD)
Sessions
Saving the battery
Because it is not possible to view the screen when the backlight is off, the following state diagrams could be used to offer a properly working screen saver with notification information.
| state number | state name | transitions |
|---|---|---|
| 0 | screen off | any key to go state 1 incoming call to go to state 3 |
| 1 | screen saver | screen unlock key to go to state 2 time out of x seconds to go to state 0 |
| 2 | normal screen | screen lock key to go to state 1
time out of y seconds to go to state 0 |
| 3 | protected normal screen offering an application to handle only an incoming call | end of call to go to state 1 screen unlock key to go to state 2 (to be able to use other applications) |
Optionally unlocking the screen (all transitions to state 2) might require to enter the user's password.
Architectural Details
(TBD)
Implementation Recommendations
(TBD)
Interactions
(TBD)
Unresolved Issues
(TBD)
Questions and Answers
(TBD)
