Holger's qtopia repo: Changes to 'master'

[git at git.openmoko.org]

 src/applications/clock/alarm.cpp        |   28 +++++++++----
 src/applications/clock/alarm.h          |   14 ++++++-
 src/applications/datebook/alarmview.cpp |   21 ++++++++++
 src/applications/datebook/alarmview.h   |    4 ++
 src/libraries/qtopia/odeviceusage.cpp   |   67 +++++++++++++++++++++++++++++++
 src/libraries/qtopia/odeviceusage.h     |   45 +++++++++++++++++++++
 src/libraries/qtopia/qtopia.pro         |    5 ++
 7 files changed, 174 insertions(+), 10 deletions(-)

New commits:
commit bc3319c6f1331750d54079fa8907ae950cc84507
Author: Holger Freyther <zecke at selfish.org>
Date:   Sun Oct 5 12:15:47 2008 +0200

    [suspend/resume] Do not suspend while we show an alarm
        Introduce ODeviceUsage which is talking with the ompowerd
        to lock any kind of resource.
    
        Switch clock and datebook over to this class. Be friendly when
        we try to unlock more often than it was locked, unlock on
        destruction of ODeviceUsage.
    
        Specially in alarmview.cpp it is hard to figure out when to
        lock/unlock. Everytime we start/stop mAlarmTimer I added a
        lock/unlock.
    
        (untested)

commit 740c29dc4e8a022f410278b61acfe8b7cd67b9a1
Author: Holger Freyther <zecke at selfish.org>
Date:   Sun Oct 5 05:50:07 2008 +0200

    [clock] Play the alarm until the user is doing something with the device
        Instead of only ringing a couple of times and then giving up
        try the best to wake up the user. This involves ringing until the
        user clicks ok. In the worse case the battery will go empty while
        it is attempted to wake up the user but at least we tried. In the
        majority of cases the alarm is set because it is important.