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