DisplayAlarmRecord (Was Re: [Cosmo-dev] ContentItem sharing)

[Grant Baillie]

On 15 Mar, 2007, at 09:10, Morgen Sagen wrote:

>
> On Mar 13, 2007, at 10:59 AM, Grant Baillie wrote:
> ...
>
>> - NoteRecord currently has:
>>     # Note.reminders?  (Translator not implemented yet)
>>     reminderTime =3D eim.field(eim.DecimalType(digits=3D20, =20
>> decimal_places=3D0))
>>
>>     [=C3] My understanding here is that Bug 7915 (and iCalendar =20
>> interoperability)
>>     imply that we should have a separate ReminderRecord (or, =20
>> AlarmRecord, if
>>     we're going with iCalendar-like syntax). What do people think =20
>> of that?
>
> Is that what the DisplayAlarmRecord is for?

Yes, it is. I had somehow missed that that was there (probably b/c I =20
did the wrong word search, I'd guess).

> Actually I don't remember the relationship between =20
> Note.reminderTime field and DisplayAlarmRecord.

Here's what you wrote in

<http://lists.osafoundation.org/pipermail/cosmo-dev/2007-January/=20
002560.html>

> We decided to add a reminderTime field to NoteRecord to represent an
> absolute reminder time for non-event items.  Once a note with a
> reminder is stamped as an event, the NoteRecord.reminderTime field
> will be set to nil, and a DisplayAlarmRecord instance will be emitted.

It seems to me we should go with the ICalendar-like scheme here: have =20=

a DisplayAlarmRecord for any ItemRecord with alarms (user reminders, =20
in Chandler terminology). It should be an error to set a "relative" =20
alarm (i.e. one with a trigger value like "-PT15M") on something that =20=

doesn't have an EventRecord.

Cosmo folks, is that your expectation?

--Grant