ui/android: Fix Resource meta-data sharing with ResourceManager.

ui/android/resources/resource.h

Index: ui/android/resources/resource.h
diff --git a/ui/android/resources/resource.h b/ui/android/resources/resource.h
new file mode 100644
index 0000000000000000000000000000000000000000..32768bd977f9a0348aad4a766cecdea1a182027d
--- /dev/null
+++ b/ui/android/resources/resource.h
@@ -0,0 +1,44 @@
+// Copyright 2017 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_ANDROID_RESOURCES_RESOURCE_H_
+#define UI_ANDROID_RESOURCES_RESOURCE_H_
+
+#include "cc/resources/scoped_ui_resource.h"
+#include "third_party/skia/include/core/SkBitmap.h"
+#include "ui/android/ui_android_export.h"
+#include "ui/gfx/geometry/rect.h"
+
+namespace ui {
+
+class UI_ANDROID_EXPORT Resource {
+ public:
+  enum class Type { BITMAP, NINE_PATCH_BITMAP, UNKNOWN };

[mdjones, 2017/03/10 18:12:00]

What is UNKNOWN used for?

[Khushal, 2017/03/10 19:19:24]

I was planning on using it for sub-classes outside on ui/. Like for the Toolbar
resource. But may be we can still have these types be declared in the enum here,
even if the sub-class exists in chrome/?

[mdjones, 2017/03/13 16:47:06]

I don't think we should have chrome specific things here. I think resources
should be clearly defined; I believe there are few reasons to need to sub-class
this. If there needs to be extra logic, I think that should live in the objects
that use these resources rather than in the resources themselves.

[Khushal, 2017/03/13 21:03:25]

My plan for getting rid of padding/aperture coming from ViewResourceAdapter was
to add a Resource sub-class in chrome/ for the Toolbar and plumb the values from
there more clearly. Specifically I think what we end up needing is
tab_strip_height, the height of the toolbar_with_no_shadow, whether
shadow_is_at_bottom and the position of the location bar to build the
ToolbarLayer. We could add TOOLBAR type to the enum here but have the sub-class
live in chrome/? I was inclined on tagging this data with the resource since it
is necessary to draw it correctly using cc. Any other ideas to structure this
better?

+
+  Resource();
+  virtual ~Resource();
+
+  virtual std::unique_ptr<Resource> CreateForCopy();
+  void SetUIResource(std::unique_ptr<cc::ScopedUIResource> ui_resource,
+                     const gfx::Size& size_in_px);
+  size_t EstimateMemoryUsage() const;
+
+  cc::ScopedUIResource* ui_resource() const { return ui_resource_.get(); }
+  gfx::Size size() const { return size_; }
+  Type type() const { return type_; }
+
+ protected:
+  Resource(Type type);
+
+ private:
+  const Type type_;
+
+  // Size of the bitmap in physical pixels.
+  gfx::Size size_;
+  std::unique_ptr<cc::ScopedUIResource> ui_resource_;
+};
+
+}  // namespace ui
+
+#endif  // UI_ANDROID_RESOURCES_RESOURCE_H_