Add InputEvent and EventPacket types for batched input delivery

content/common/input/input_event.h

+// Copyright (c) 2013 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 CONTENT_COMMON_INPUT_INPUT_EVENT_H_
+#define CONTENT_COMMON_INPUT_INPUT_EVENT_H_
+
+#include "base/basictypes.h"
+#include "content/common/content_export.h"
+#include "content/common/input/input_event_state.h"
+
+namespace content {
+
+class CONTENT_EXPORT InputEvent {
+ public:
+  enum Type {

[nduca, 2013/08/15 01:22:46]

can we use pure inheritance here and make this a pure virtual base class? Then
use ipc traits to get this to serialize sanely across the wire (and or make
explicit methods for conversion to ipc messages.

reason being: it'd be nice to see on this class the things we expect out of all
input events but not how they're implemented serialized etc.

[jdduke (slow), 2013/08/15 15:23:45]

I think we need some kind of residual type data here to be able to serialize
based any given InputEvent (e.g., a vector of InputEvent's).  I could be wrong
(I'd love to be wrong), but this is the pattern I've seen used elsewhere
(cc::DrawQuad).  Can the IPC traits macro magic accomplish this automatically?

+    GENERIC,
+    WEB,
+  };
+
+  virtual ~InputEvent();
+
+  Type type;
+  int64 id;
+
+ protected:
+  InputEvent(Type type, int64 id);
+
+ private:
+  DISALLOW_COPY_AND_ASSIGN(InputEvent);
+};
+
+} // namespace content
+
+#endif // CONTENT_COMMON_INPUT_INPUT_EVENT_H_