- From: Marcos Caceres <w3c@marcosc.com>
- Date: Thu, 9 May 2013 21:36:04 +0100
- To: Christophe Dumez - SISA <ch.dumez@partner.samsung.com>, "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Jake Verbaten <raynos2@gmail.com>, public-script-coord <public-script-coord@w3.org>
On Wednesday, May 8, 2013 at 8:29 PM, Tab Atkins Jr. wrote:
> On Wed, May 8, 2013 at 12:14 PM, Jake Verbaten <raynos2@gmail.com (mailto:raynos2@gmail.com)> wrote:
> > > which means that it's impossible
> > > to know what the alarm id is for cancelling until it's too late to
> > > cancel it.
> >
> >
> >
> > I've actually interpreted the API wrongly. add returns once the device
> > succesfully tells you that the alarm has been registered.
> >
> > You actually listen to the actual alarm going of by using
> > `navigator.setMessageHandler("alarm", onAlarmFired);` which I missed on my
> > first scan.
>
>
>
> Oh, I see! Yes, that's very unclear, though this is partially due to
> my ignorance of "system messages". It negates several of my issues,
> though.
>
> In that case, scratch my comments about cancellable futures. Instead,
> keep .remove(), but just let it accept the future returned by .add().
> No reason to abstract through a string when you've got a handy object
> already there. That way you can kill the .id property entirely.
>
> My comments about potentially killing .clear() stand, though. It may
> be convenient to keep, but we can drop it if it can't justify itself.
>
I've filed a but about killing clear.
https://github.com/sysapps/web-alarms/issues/39
Christophe, any thoughts?
--
Marcos Caceres
Received on Thursday, 9 May 2013 20:36:39 UTC