alarm points

This is what i saw we semi-agreed on, correct me if I'm wrong :D

Have 3 layers
 - atd
 - libgpe-alarm
 - <app>

Apps can register as many alarms as they want, but gpe-calendar will do
only one. It will itself handle recurrance.

libgpe-alarm will have (eg.)
  gpe_set_alarm (unixtime, "program")
  gpe_set_alarm_message (unixtime, "title", "message");

atd only needs to be able to run a random program, no more (yet ;)
gpe_set_alarm_message should just call gpe_set_alarm (unixtime,
"gpe-announce <args>");

gpe-calendar callbacks will go back to gpe-calendar. That will then call
gpe-announce and set the next alarm needed.

Notes:
nils wants IPC in libgpe-alarm
PaxAnima wants recurrance in libgpe-alarm

The palmos developer's companion section on alarms is at
http://tinfpc2.vub.ac.be/manuals/palm/devdoc/SystemFeatures.html#924958
 We should also look at opiealarm and ipaqalarm/uschedule
(http://www.ohse.de/uwe/uschedule.html)

The log is at:
http://handhelds.org/~mibus/irc_alarm_meeting.log

Discussions and notes can be put here:
http://handhelds.org/z/wiki/IRCAlarmMeetingLog
mibus

-- 
Robert Mibus <mibus_at_bigpond.com>
Even if you can deceive people about a product through misleading
statements, sooner or later the product will speak for itself.
 (Hajime Karatsu)