Re: Vibration

We are already at the stage of being ready to enter PR on this draft which already has implementations.  

These sound like v2 features that we should consider for the next revision.

Do you agree.

regards, Frederick

Frederick Hirsch, Nokia
Chair DAP
@fjhirsch



On Nov 13, 2014, at 12:34 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Thu, Oct 9, 2014 at 3:32 PM, Kostiainen, Anssi
> <anssi.kostiainen@intel.com> wrote:
>> On 09 Oct 2014, at 15:46, Anne van Kesteren <annevk@annevk.nl> wrote:
>>> Is there anything in http://dev.w3.org/2009/dap/vibration/ you would
>>> have done differently today in terms of the API? We want to add
>>> vibration support to the notifications API as part of a general set of
>>> behaviors, see https://github.com/whatwg/notifications/issues/22 Was
>>> just wondering if the API should be the same or slightly different. In
>>> particular overloading long with a sequence of long does not seem
>>> great.
>> 
>> We tried to keep the scope as tight as possible and did not add any extras, thus not much to do differently.
> 
> Okay.
> 
> I was wondering if you could provide the following features.
> 
> * A dedicated name for the method argument, so that I can use it
> elsewhere. E.g. VibratePattern or some such.
> * A standalone algorithm that performs the additional validation
> required and normalizes the input.
> * A standalone algorithm that performs the actual vibration.
> 
> This should make it possible to introduce notifications that vibrate
> while reusing the vibration infrastructure the Vibration API
> implicitly (hopefully soon explicitly) provides.
> 
> 
> -- 
> https://annevankesteren.nl/
>

Received on Friday, 14 November 2014 15:59:35 UTC