chrome/android: Update toolbar drawing in native.

chrome/android/java/src/org/chromium/chrome/browser/compositor/resources/ResourceFactory.java

Index: chrome/android/java/src/org/chromium/chrome/browser/compositor/resources/ResourceFactory.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/compositor/resources/ResourceFactory.java b/chrome/android/java/src/org/chromium/chrome/browser/compositor/resources/ResourceFactory.java
new file mode 100644
index 0000000000000000000000000000000000000000..06237d7e8ceb6718bece28a3e384cdc041a84788
--- /dev/null
+++ b/chrome/android/java/src/org/chromium/chrome/browser/compositor/resources/ResourceFactory.java
@@ -0,0 +1,27 @@
+// 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.
+
+package org.chromium.chrome.browser.compositor.resources;
+
+import android.graphics.Rect;
+
+import org.chromium.base.annotations.JNINamespace;
+
+/**
+ * Utility class for creating native resources.
+ */
+@JNINamespace("android")
+public class ResourceFactory {
+    public static long createToolbarContainerResource(

[mdjones, 2017/03/16 21:01:47]

Are we going to do something similar for the crushed sprite stuff?

[David Trainor- moved to gerrit, 2017/03/17 07:41:22]

I think that (crushed sprite) could go in ui/ since it doesn't require something
chrome/ specific?

[mdjones, 2017/03/17 15:38:10]

That makes sense, I was thinking about it as part of contextual search, but
crushed sprites in general aren't chrome specific.

[Khushal, 2017/03/17 23:02:58]

Yeah. CrushedSprite in next patch. That should be all in ui/

[Khushal, 2017/03/17 23:49:44]

I looked at CrushedSprite and they are funkier than I thought. With the regular
Resource we register the bitmap with the cc::UIResourceManager since that is the
bitmap we want to draw with, and we only expose the UIResource. We don't want to
expose the raw bitmap and have callers use it directly, since that would mean
multiple UIResources could be generated for the same bitmap.

The CrushedSpriteResource exposes the raw bitmap because the bitmap to use is
generated for each frame using this bitmap, and then it is set on the layer
directly. I don't think we want to have a base interface/class that exposes the
bitmap just for this use-case. The Crushed sprite stuff is already separate from
the rest of resource management. Its probably easier to let it stay that way.
+dtrainor@, thoughts?

+            Rect toolbarPosition, Rect locationBarPosition, int shadowHeight) {
+        return nativeCreateToolbarContainerResource(toolbarPosition.left, toolbarPosition.top,
+                toolbarPosition.right, toolbarPosition.bottom, locationBarPosition.left,
+                locationBarPosition.top, locationBarPosition.right, locationBarPosition.bottom,
+                shadowHeight);
+    }
+
+    private static native long nativeCreateToolbarContainerResource(int toolbarLeft, int toolbarTop,
+            int toolbarRight, int toolbarBottom, int locationBarLeft, int locationBarTop,
+            int locationBarRight, int locationBarBottom, int shadowHeight);
+}