Add display of available bluetooth devices, and mechanism for retrieving the list.

chrome/browser/ui/webui/options/chromeos/system_options_handler.cc

 // Copyright (c) 2011 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 "chrome/browser/ui/webui/options/chromeos/system_options_handler.h"
 
 #include <string>
 
 #include "base/basictypes.h"
 #include "base/command_line.h"
@@ skipping 55 matching lines @@
   localized_strings->SetString("sensitivityMore",
       l10n_util::GetStringUTF16(
           IDS_OPTIONS_SETTINGS_SENSITIVITY_MORE_DESCRIPTION));
 
   localized_strings->SetString("bluetooth",
       l10n_util::GetStringUTF16(IDS_OPTIONS_SETTINGS_SECTION_TITLE_BLUETOOTH));
   localized_strings->SetString("enableBluetooth",
       l10n_util::GetStringUTF16(IDS_OPTIONS_SETTINGS_BLUETOOTH_ENABLE));
   localized_strings->SetString("findBluetoothDevices",
       l10n_util::GetStringUTF16(IDS_OPTIONS_SETTINGS_FIND_BLUETOOTH_DEVICES));
+  localized_strings->SetString("bluetoothScanning",
+      l10n_util::GetStringUTF16(IDS_OPTIONS_SETTINGS_BLUETOOTH_SCANNING));
+  localized_strings->SetString("bluetoothDeviceConnected",
+      l10n_util::GetStringUTF16(IDS_OPTIONS_SETTINGS_BLUETOOTH_CONNECTED));
+  localized_strings->SetString("bluetoothDeviceNotPaired",
+      l10n_util::GetStringUTF16(IDS_OPTIONS_SETTINGS_BLUETOOTH_NOT_PAIRED));
 
   localized_strings->SetString("language",
       l10n_util::GetStringUTF16(IDS_OPTIONS_SETTINGS_SECTION_TITLE_LANGUAGE));
   localized_strings->SetString("languageCustomize",
       l10n_util::GetStringUTF16(IDS_OPTIONS_SETTINGS_LANGUAGES_CUSTOMIZE));
   localized_strings->SetString("modifierKeysCustomize",
       l10n_util::GetStringUTF16(
           IDS_OPTIONS_SETTINGS_LANGUAGES_MODIFIER_KEYS_CUSTOMIZE));
 
   localized_strings->SetString("accessibilityTitle",
@@ skipping 23 matching lines @@
       ->HasSwitch(switches::kEnableBluetooth)) {
     web_ui_->CallJavascriptFunction(
         "options.SystemOptions.ShowBluetoothSettings");
   }
 }
 
 void SystemOptionsHandler::RegisterMessages() {
   DCHECK(web_ui_);
   web_ui_->RegisterMessageCallback("accessibilityChange",
       NewCallback(this, &SystemOptionsHandler::AccessibilityChangeCallback));
+  web_ui_->RegisterMessageCallback("bluetoothEnableChange",
+      NewCallback(this, &SystemOptionsHandler::BluetoothEnableChangeCallback));
+  web_ui_->RegisterMessageCallback("findBluetoothDevices",
+      NewCallback(this, &SystemOptionsHandler::FindBluetoothDevicesCallback));
 }
 
 void SystemOptionsHandler::AccessibilityChangeCallback(const ListValue* args) {
   std::string checked_str;
   args->GetString(0, &checked_str);
   bool accessibility_enabled = (checked_str == "true");
 
   chromeos::accessibility::EnableAccessibility(accessibility_enabled, NULL);
 }
+
+void SystemOptionsHandler::BluetoothEnableChangeCallback(const ListValue* args)
+{

[James Hawkins, 2011/10/04 20:43:39]

Opening brace goes on the same line as the method.

[kevers, 2011/10/05 14:23:01]

Exceeded 80 character line limit with the opening brace on the same line.  Is
linebreaking before the argument preferable in this case?

+  // TODO (kevers) - Call Bluetooth API to enable or disable.
+}
+
+void SystemOptionsHandler::FindBluetoothDevicesCallback(const ListValue* args) {
+  // TODO (kevers) - Call Bluetooth API to fetch devices.
+  //                 Generate a fake list until the bluetooth API is ready.
+  //                 Afterwards keep fake list only for cases where emulating
+  //                 ChromeOS from the desktop launch.
+  GenerateFakeDeviceList();
+}
+
+void SystemOptionsHandler::GenerateFakeDeviceList() {
+  // TODO (kevers) - Send notifications asynchronously simulating that the
+  //                 process of discovering bluetooth devices takes time.
+  //                 Fire each notification using OneShotTimer with a
+  //                 varying delay.
+  BluetoothDeviceNotification("Fake Wireless Keyboard", "01-02-03-04-05",
+      "keyboard", false);
+  BluetoothDeviceNotification("Fake Wireless Mouse", "02-03-04-05-01",
+      "mouse", false);
+  BluetoothDeviceNotification("Fake Wireless Headset", "03-04-05-01-02",
+      "headset", false);
+
+  web_ui_->CallJavascriptFunction(
+      "options.SystemOptions.NotifyBluetoothSearchComplete");
+}
+
+void SystemOptionsHandler::BluetoothDeviceNotification(
+    const std::string& name,
+    const std::string& id,
+    const std::string& type,
+    bool connected) {
+  DictionaryValue device;
+  device.SetString("deviceName", name);
+  device.SetString("deviceId", id);
+  device.SetString("deviceType", type);
+  device.SetString("deviceStatus", connected ? "bluetoothDeviceConnected" :
+      "bluetoothDeviceNotPaired");

[Vince Laviano, 2011/10/04 22:03:14]

There's a distinction between paired and connected. "Paired" means that an
association has been formed (i.e., that the device is known to us), while
"connected" means that the device is currently connected. It's possible for a
paired device to be unconnected. It might be out of range, or the owner might
have paired several devices of the same class for different scenarios and
currently be using a different one.

I think that there are additional device properties that will be of interest to
the UI. It might make sense to have the bluetooth code pass either a Device
object that it defines or a DictionaryValue full of device properties to this
callback rather than having an arg for each property. This would allow the API
to remain stable as the set of interesting properties changes.

[kevers, 2011/10/05 14:23:01]

Agreed that passing in a dictionary is more flexible.  Got sloppy with the
generation of a fake list for UI testing. 

+  web_ui_->CallJavascriptFunction(
+      "options.SystemOptions.AddBluetoothDevice", device);
+}
+
+