Native to USB keycode conversion for Mac

webkit/plugins/ppapi/usb_key_code_conversion_mac.cc

Index: webkit/plugins/ppapi/usb_key_code_conversion_mac.cc
===================================================================
--- webkit/plugins/ppapi/usb_key_code_conversion_mac.cc	(revision 0)
+++ webkit/plugins/ppapi/usb_key_code_conversion_mac.cc	(working copy)
@@ -0,0 +1,35 @@
+// Copyright (c) 2012 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 "webkit/plugins/ppapi/usb_key_code_conversion.h"
+
+#include "base/basictypes.h"
+#include "third_party/WebKit/Source/WebKit/chromium/public/WebInputEvent.h"
+
+using WebKit::WebKeyboardEvent;
+
+namespace webkit {
+namespace ppapi {
+
+namespace {
+
+#define USB_KEYMAP(usb, xkb, win, mac) {usb, mac}
+#include "webkit/plugins/ppapi/usb_keycode_map.h"
+
+} // anonymous namespace
+
+uint32_t UsbKeyCodeForKeyboardEvent(const WebKeyboardEvent& key_event) {
+  if (key_event.nativeKeyCode < 0 || key_event.nativeKeyCode > 0x7f)
+    return 0;
+
+  for (uint i = 0; i < arraysize(usb_keycode_map); i++) {

[tony, 2012/03/15 16:46:28]

Nit: If we keep usb_keycode_map sorted (looks like it currently is), we could
use bsearch here.

[dmichael (off chromium), 2012/03/15 17:03:08]

If we were to use binary search, I would recommend lower_bound from <algorithm>
instead of the C bsearch.

But I think the extra code complexity isn't really necessary for something of
this size that will fit in 2kb of memory. I'm happy with it either way.

[Wez, 2012/03/15 17:10:52]

Agreed.  We can optimize the lookup later if it proves too expensive.

+    if (usb_keycode_map[i].native_keycode == key_event.nativeKeyCode)
+      return usb_keycode_map[i].usb_keycode;
+  }
+
+  return 0;
+}
+
+}  // namespace ppapi
+}  // namespace webkit