I think there should be a daemon handling this tasks. As the RTC-alarm can only be once (every day), the daemon would have to handle this to allow multiple alarms/wakeups. The daemon would have to act like this: first set the RTC-alarm - after waking up check for the scheduled event and decide if it's the correct day and run the tasks. After that decide what's the next event and set the RTC-alarm-time to the new time (or leave it as it is in case it was the wrong day). The daemon would/should have its own event database that can be filled via a dbus-interface.
As the RTC-alarm might be different from device to device it might be the clean way to let the odeviced handle the alarm-setting (communication between the two daemons via dbus) and just have a dbus-interface for that in the new daemon. That is at least what I imagine. On 5/7/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Am Mi 7. Mai 2008 schrieb David Samblas Martinez: > > > And why not implement a "execute command" option in > > the PIM Task Manager(Schedule)? > > If the neo will be able to wake up to play a sound > > and/or buzz, I suppose it can execute a shell command > > and sleep again when finished. > > > The interesting bit of this is to distinguish between dates that just had > wake > up the device, so we may go to sleep again immediately after "execution", > and > dates that happen to be "executed" while user intentionally switched on > the > device already so we mustn't go to sleep afterwards. > > /j > > > > > > (maybe this was already implemented/planned, isn't > > it?) > > --- Ryan Prior <[EMAIL PROTECTED]> escribió: > > > > > Perhaps "phone-cron" needs to be written, to take > > > anacron to the level of > > > task flexibility required for modern cell phones. > > > Cron and anacron are > > > crusty old beasts - we need something fresh and > > > sharp. > > > > > > On Tue, May 6, 2008 at 6:42 PM, Bastian Muck > > > <[EMAIL PROTECTED]> wrote: > > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > Hash: SHA1 > > > > > > > > Anachron can unfortunately run tasks once a day, > > > which you can read at the > > > > Drawback. I guess that tasks, with a > > > "remember-funktions" canot really be > > > > realized with anachron. > > > > I don't know if there is a timer, which can send > > > an wakeup-interupt, but > > > > when it exists the next upcoming task could be > > > searched an the time could be > > > > passed to the timer. Does anybody knows of such > > > timer? > > > > If not i think it should be integrated in gta03. > > > > > > > > Greetings Bastian > > > > > > > > Torfinn Ingolfsen schrieb: > > > > | Hi, > > > > | > > > > | On Tue, May 6, 2008 at 9:26 AM, Mike Baroukh > > > <[EMAIL PROTECTED]> wrote: > > > > |> About this, I was wondering if there was > > > possibility to have cron like > > > > |> tasks even if the phone is suspended ? > > > > | > > > > | You could always run something like anacron{1] > > > on the phone. As long > > > > | as yoy don't keep you phone suspended for a day > > > or more that would > > > > | work. :-) > > > > | > > > > | References: > > > > | 1) http://en.wikipedia.org/wiki/Anacron > > > > > > > > -----BEGIN PGP SIGNATURE----- > > > > Version: GnuPG v1.4.7 (MingW32) > > > > Comment: Using GnuPG with Mozilla - > > > http://enigmail.mozdev.org > > > > > > > > > > > > > iD8DBQFIIOz2lYiDScJJ+7QRAquEAKC5JcE/JSzJBMg3nv0B9eZymrjgUACgldfG > > > > k9r7LB1DceHTxuqMFYgeAtI= > > > > =JGQI > > > > -----END PGP SIGNATURE----- > > > > > > > > > > > > > > > > _______________________________________________ > > > > Openmoko community mailing list > > > > community@lists.openmoko.org > > > > > > > http://lists.openmoko.org/mailman/listinfo/community > > > > > > > > _______________________________________________ > > > Openmoko community mailing list > > > community@lists.openmoko.org > > > http://lists.openmoko.org/mailman/listinfo/community > > > > > > > > > > > ______________________________________________ > > Enviado desde Correo Yahoo! La bandeja de entrada más inteligente. > > > > > > _______________________________________________ > > Openmoko community mailing list > > community@lists.openmoko.org > > http://lists.openmoko.org/mailman/listinfo/community > > > > > > _______________________________________________ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community >
_______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community