Pepper/Flapper: First pass at context menu implementation.

ppapi/cpp/private/flash_menu.h

Index: ppapi/cpp/private/flash_menu.h
diff --git a/ppapi/cpp/private/flash_menu.h b/ppapi/cpp/private/flash_menu.h
new file mode 100644
index 0000000000000000000000000000000000000000..a5d4408a8b605dcc69db12bac806cb7fb9247c68
--- /dev/null
+++ b/ppapi/cpp/private/flash_menu.h
@@ -0,0 +1,36 @@
+// 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.
+
+// TODO(viettrungluu): This (and the .cc file) contain C++ wrappers for some
+// things in ppapi/c/private/ppb_flash_menu.h. This is currently not used in (or
+// even compiled with) Chromium.
+
+#ifndef PPAPI_CPP_PRIVATE_FLASH_MENU_H_
+#define PPAPI_CPP_PRIVATE_FLASH_MENU_H_
+
+#include "ppapi/c/private/ppb_flash_menu.h"
+#include "ppapi/cpp/resource.h"
+
+namespace pp {
+
+class CompletionCallback;
+class Instance;
+class Point;
+
+namespace flash {
+
+class Menu : public Resource {

[brettw, 2011/01/31 18:19:49]

Is it really necessary to have C++ wrappers for this? I'd prefer to not have
wrappers for the private stuff since it seems like it might encourage random
people to use them, and makes the C++ wrapper library larger for no reason.
Especially since this wrapper is so simple.

[viettrungluu, 2011/01/31 19:01:41]

It makes the Flapper-side code nicer (e.g., no need to explicitly get the
interface). For IP reasons (especially if it gets turned into a non-private
interface), I'd rather that this live in the Chromium tree. (It doesn't get
linked in to the standard C++ wrapper library.)

+ public:
+  // TODO(viettrungluu): Write a proper C++ wrapper of |PP_Flash_Menu|.
+  Menu(const Instance& instance, const struct PP_Flash_Menu* menu_data);
+
+  int32_t Show(const Point& location,
+               int32_t* selected_id,
+               const CompletionCallback& cc);
+};
+
+}  // namespace flash
+}  // namespace pp
+
+#endif  // PPAPI_CPP_PRIVATE_FLASH_H_