Re: Ambient light events and proximity events in CR! Fwd: Ambient Light Events, and Proximity Events are Candidate Recommendations (Call for Implementations)

*Hi Anssi,*

On 30 December 2013 14:42, Kostiainen, Anssi <anssi.kostiainen@intel.com>wrote:

> Hi Francesco, All,
>
> On 24 Dec 2013, at 19:01, Francesco Iovine <f.iovine@gmail.com> wrote:
>
> > Hi guys,
> >
> > Mozilla implemented the DeviceLightEvent for Firefox, Firefox Mobile and
> Firefox OS.
> >
> > I wrote a Xmas-themed Ambient Light API article on MDN about it:
> >
> >
> https://developer.mozilla.org/en-US/Apps/Developing/gather_and_modify_data/Responding_to_light_conditions
>
> Thanks for sharing the article and the cool demo :)
>
> It seems you just documented a use case that would benefit from
> LightLevelEvent. In your demo you need to guess the lux breakpoints for
> morning, evening, night etc. while an implementation might be in a better
> position to know what are the typical lux ranges for the user’s current
> environment that are considered dim, normal, and bright. For example, in
> the Northern Finland the sun never comes above the horizon this time of
> year.
>

*What you said makes sense: I had to guess the lux breakpoints, and it was
neither easy nor precise, but in my demo I had 4 states (snow, morning,
evening, night) instead of 3 (dim, normal, bright) and the breakpoints of
the LightLevelEvent (50lux, 10000lux) didn't fit my needs (special effects
in a e-book reader app to be used mainly in a room with a dim light).
However I think that the LightLevelEvent would be useful when improving
readability in a e-book reader app or user experience in a HTML5 game based
on the ambient light for some features, for example. *

>
>
> > Hope it helps!
> >
> > However it looks like the work on the LightLevelEvent Interface has
> stopped:
> >
> > https://bugzilla.mozilla.org/show_bug.cgi?id=842952
> >
> > Do you have further news on the implementations?
> > Is the LightLevelEvent specification stable?
>
> Re the spec stability, I proposed the following change to the spec to
> combine the interfaces:
>
>   http://lists.w3.org/Archives/Public/public-device-apis/2013Apr/0043.html
>
> This was +1’d by Doug and Anne. Given the known implementations only
> implement DeviceLightEvent, we could merge the value attribute of the
> LightLevelEvent interface into the DeviceLightEvent and rename it to e.g.
> state as I proposed.
>

*+1 also by me, it looks like a great idea. I'm going to keep the demo
up-to-date with the latest specification/implementation as soon as it comes
available, and keep on building demos to promote the W3C Device APIs: I
think that such APIs are a key factor for the success of the Web Platform
and Open Web Apps, especially for mobile devices.*


>
> The only concern is with the firing frequency, but this is not a major
> issue.
>
> Does anyone have concerns with merging the DeviceLightEvent and
> LightLevelEvent interfaces as described in the mail above?
>

> [For consistently, we should keep the DeviceProximityEvent and
> UserProximityEvent in sync if we do changes here, but that warrants another
> thread if we proceed with this change.]
>
> > For everyone who celebrates Christmas, wish you a wonderful festive
> season!
>
> Thanks!
>
> -Anssi
>



*Best,*

*Francesco <https://twitter.com/franciov>*