Re: alarms

On Mon, 2002-12-02 at 03:04, Philip Blundell wrote:
> So, back in September we had this IRC summit to decide on a strategy for
> alarms. From what I remember, the two main actions arising from this
> were that Nils was going to fix atd so that it worked and get a new
> release made, and mibus was going to create this wrapper library
> (tentatively named libredalert) for apps to use.
Yup...

> I'm not very clear what the current status is with this stuff. Are
> these pieces of code now working well enough that programs like
> gpe-calendar can use them?

Probably not... If you recall some emails I sent you when I wrote what
is now in CVS as libredalert, I told you that the API in there ATM is
not enough for all possible uses, but to change that required some minor
changes to atd. I don't know if Nils' changes affect that too.

Basically, atd *requires* a filename in the form of [time].[pid],
whereas [pid] is useless for us, so we'd be better off having (IIRC)
[time].[app]-[event id]; [app] should be generic ("calendar") so a GPE
competitor could share the sqlite DB and also the alarms. The event id
should be whatever the key in the DB is... that makes it simple to
remove alarms ('rm -f /.../*.app-eventid').

IIRC i mentioned what the header in libredalert would have to change to,
but didn't give you the code. (I had a working copy at the time, but it
was only about four lines different from the current libredalert).

I've got holidays now, but I can't promise to get to look at it soon. I
*am* hoping to get it done by the end of the holidays (ie.
february-ish), preferably earlier ;)

As for the name, I don't really care one way or the other. libredalert
was just something to call it "for now"... I never even intended for it
to have that name when it hit CVS :)

> p.
mibus
PS. please don't shoot me if i missed something ;)

-- 
Robert Mibus  <mibus@iprimus.com.au>
Why cant you use windows CDs for drink coasters?
You'd spill your coffee, It's not a stable platform :)