Migrates battery_status from content/renderer/ to WebKit/platform/

third_party/WebKit/Source/platform/battery/BatteryStatusDispatcher.cpp

+// Copyright 2014 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.
+
+#include "platform/battery/BatteryStatusDispatcher.h"
+
+#include "platform/base/Bind.h"
+#include "platform/battery/BatteryStatus.h"
+#include "platform/battery/BatteryStatusListener.h"
+#include "public/platform/Platform.h"
+#include "wtf/Assertions.h"
+
+namespace blink {
+
+BatteryStatusDispatcher::BatteryStatusDispatcher(BatteryStatusListener* listener)
+    : m_listener(listener)
+{
+    ASSERT(m_listener);
+
+    Platform::current()->connectToRemoteService(mojo::GetProxy(&m_monitor));
+    // m_monitor can be null during testing.
+    if (m_monitor)
+        queryNextStatus();
+}
+
+BatteryStatusDispatcher::~BatteryStatusDispatcher() {}
+
+void BatteryStatusDispatcher::queryNextStatus()
+{
+    m_monitor->QueryNextStatus(
+        bindInstanceToMethod(&BatteryStatusDispatcher::onDidChange, this));

[haraken, 2016/01/25 02:00:28]

Why can't we just use WTF::bind?

[Anand Mistry (off Chromium), 2016/01/25 06:00:24]

Why use bind at all? This doesn't need to be thread-safe (mojo callbacks are
explicitly not thread-safe) and |this| is unretained, so just pass in a lambda.
Don't know how OK that is with the style though.

[Yuki, 2016/01/26 07:50:32]

Note that base::Bind and WTF::bind are NOT compatible.  We cannot use WTF::bind
in this case because Mojo requires base::Callback.

+}
+
+void BatteryStatusDispatcher::onDidChange(device::BatteryStatusPtr batteryStatus)
+{
+    // m_monitor can be null during testing.
+    if (m_monitor)
+        queryNextStatus();
+
+    DCHECK(batteryStatus);
+
+    BatteryStatus status(batteryStatus->charging, batteryStatus->charging_time, batteryStatus->discharging_time, batteryStatus->level);
+    m_listener->onUpdateBatteryStatus(status);
+}
+
+} // namespace blink