[maemo-developers] [maemo-developers] Maemo Alarm/Notifier Interface
From: Florian Boor florian.boor at kernelconcepts.deDate: Thu Jan 12 19:58:30 EET 2006
- Previous message: [maemo-developers] Maemo Alarm/Notifier Interface
- Next message: [maemo-developers] Maemo Alarm/Notifier Interface
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, Devesh Kothari wrote: > Great this is feedback I was looking for. Now just to bring on same page > again > > First the end user use cases > 1. An application e.g Calender or task wanting to alart and notify the > user of scheduled events. This notification should have a certain > accepted granularity and delivery promise > - Resolution of most end user use case can live with 1 minutes > granularity [IMHO] In theory yes... but an alarm clock going off a minute too late doesn't really look good. If we can do it better we should... > - Events must be delivered regardless of the device state e.g sleep, > deep sleep or poweroff state [but with battery plugged in] I'm not sure if poweroff is really necessary... it would be cool if it is possible but i suppose we could live without this if it is complicated to implement. > - User should be able to schedule Events/Notification in any future > time e.g my mothers birthday which is 8 months away. Definitely... > Every other use case is more secondary use case > 2. User is able to work on all scheduled events from one common point > UI (e.g as simon pointed, in a cinema, want to silent all alarms, cancel > or enable alarms). > - You can argue that switching off the device speaker would result the > same, though you might have the nuisance of screen turn ons. > - The ability to cancel/enable alarm might make things complicated for > application developers, as then events not delivered to the registered > apps, somebody need to tell them that the alarm was either cancelled or > rescheduled, so they can reach a sync state. Well... usually applications will use both an alarm signal and some notification on screen. If the alarm signal is disabled by a system state and no user input received the device should just go to sleep again. Some system message indicating a missed alarm if the evice state is changed might be another possible way to deal with this. >>From a Developer Perspective ... > 3. It would also be useful that the implemented solution is also > available/complaint/builds upon other solutioins like that mentioned > about hh.org and iPAQs Would be useful - in particular for gpe-calendar :-) > I think it would be good idea to have a wiki page? My objective is > quite achieved that there is community participation, and people inside > nokia need to look into what the community had wanted and what was > delivered :) even when I know product schedules and requirements are > highest priority [read as , you wont get always what you wanted ;)]. Well... your summary would be a good start for a wiki page :-) Greetings Florian -- The dream of yesterday Florian Boor is the hope of today Tel: 0271-771091-14 and the reality of tomorrow. Fax: 0271-771091-19 [Robert Hutchings Goddard, 1904] florian.boor at kernelconcepts.de 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8
- Previous message: [maemo-developers] Maemo Alarm/Notifier Interface
- Next message: [maemo-developers] Maemo Alarm/Notifier Interface
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]