Added material design mouse hover feedback support.

ui/views/animation/ink_drop_consumer.h

Index: ui/views/animation/ink_drop_consumer.h
diff --git a/ui/views/animation/ink_drop_consumer.h b/ui/views/animation/ink_drop_consumer.h
new file mode 100644
index 0000000000000000000000000000000000000000..84b7e3555d3e498c029edd4d0705fcde09631457
--- /dev/null
+++ b/ui/views/animation/ink_drop_consumer.h
@@ -0,0 +1,29 @@
+// Copyright 2015 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 UI_VIEWS_ANIMATION_INK_DROP_CONSUMER_H_
+#define UI_VIEWS_ANIMATION_INK_DROP_CONSUMER_H_
+
+#include "base/macros.h"
+#include "ui/views/views_export.h"
+
+namespace views {
+
+// Pure virtual base class that defines the API required of the ink drop

[Evan Stade, 2015/11/12 19:31:46]

nit: s/Pure virtual base class/Interface/

[bruthig, 2015/12/23 20:31:35]

Done.

+// consuming surface such that the InkDropController can interact with it.
+class VIEWS_EXPORT InkDropConsumer {

[Evan Stade, 2015/11/12 19:31:46]

why is this not part of InkDropHost? It looks pretty funky to write
CreateInkDropController(this, this); (especially since it's this, this every
time it's called)

[bruthig, 2015/11/12 21:16:12]

The thinking is that the InkDropHost could host multiple ink drops, with
different sizes and locations whereas there will be a one-to-one relationship of
InkDropConsumers to InkDropAnimationControllers.

Point taken tho, I will try and add a CreateInkDropController() method that
takes a single parameter, since that will be the common use case.

[bruthig, 2015/12/23 20:31:35]

The InkDropConsumer has been removed.

+ public:
+  InkDropConsumer() {}
+  virtual ~InkDropConsumer() {}
+
+  // Returns true if the InkDropHover should be shown.
+  virtual bool ShouldShowInkDropHover() = 0;
+
+ private:
+  DISALLOW_COPY_AND_ASSIGN(InkDropConsumer);
+};
+
+}  // namespace views
+
+#endif  // UI_VIEWS_ANIMATION_INK_DROP_CONSUMER_H_