[sensors]: Introduce the Generic Sensor API.

third_party/WebKit/Source/modules/sensor/SensorReadingEvent.h

Index: third_party/WebKit/Source/modules/sensor/SensorReadingEvent.h
diff --git a/third_party/WebKit/Source/modules/sensor/SensorReadingEvent.h b/third_party/WebKit/Source/modules/sensor/SensorReadingEvent.h
new file mode 100644
index 0000000000000000000000000000000000000000..9d9f46dba91407b5b23be7a050d398c4faf1f43a
--- /dev/null
+++ b/third_party/WebKit/Source/modules/sensor/SensorReadingEvent.h
@@ -0,0 +1,59 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef SensorReadingEvent_h
+#define SensorReadingEvent_h
+
+#include "modules/EventModules.h"
+#include "modules/sensor/SensorReading.h"
+#include "modules/sensor/SensorReadingEventInit.h"
+#include "platform/heap/Handle.h"
+
+namespace blink {
+
+class SensorReadingEvent : public Event {
+    DEFINE_WRAPPERTYPEINFO();
+
+public:
+    static SensorReadingEvent* create()
+    {
+        return new SensorReadingEvent;
+    }
+
+    static SensorReadingEvent* create(const AtomicString& eventType)
+    {
+        return new SensorReadingEvent(eventType);
+    }
+
+    static SensorReadingEvent* create(const AtomicString& eventType, SensorReading& reading)
+    {
+        return new SensorReadingEvent(eventType, reading);
+    }
+
+    static SensorReadingEvent* create(const AtomicString& eventType, const SensorReadingEventInit& initializer)
+    {
+        return new SensorReadingEvent(eventType, initializer);
+    }
+
+    ~SensorReadingEvent() override;
+
+    DECLARE_VIRTUAL_TRACE();

[timvolodine, 2016/05/24 15:30:35]

nit: put below

[riju_, 2016/05/25 15:07:18]

Done.

+
+    SensorReading* reading() { return m_reading; }

[timvolodine, 2016/05/24 15:30:35]

const method? and what about returning pointer to const reading?
the latter question also applies to sensor.reading

[riju_, 2016/05/25 15:07:18]

Const method yes. Checked with the other getters, and looks like this is the
norm.

[timvolodine, 2016/05/25 15:40:22]

alright, could you file a crbug and put a TODO to consider making it return
pointer to const? generally don't think we want the users be able to change
m_reading.

+    const AtomicString& interfaceName() const override;
+
+    SensorReadingEvent();

[timvolodine, 2016/05/24 15:30:35]

should constructors be protected/private?

[riju_, 2016/05/25 15:07:18]

Done.

+    SensorReadingEvent(const AtomicString& eventType);
+    SensorReadingEvent(const AtomicString& eventType, SensorReading&);
+    SensorReadingEvent(const AtomicString& eventType, const SensorReadingEventInit& initializer);
+
+protected:
+    Member<SensorReading> m_reading;
+};
+
+DEFINE_TYPE_CASTS(SensorReadingEvent, Event, event, event->interfaceName() == EventNames::SensorReadingEvent, event.interfaceName() == EventNames::SensorReadingEvent);
+
+} // namepsace blink
+
+#endif // SensorReadingEvent_h