[Android] Binary files for Fixed default bookmark shortcut icon drawing.

[Android] Binary files for Fixed default bookmark shortcut icon drawing.

This contains the binary drawables related to this CL:
https://codereview.chromium.org/15992008/

BUG=241380
R=tedchoc@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=203994

[Ted C, 2013-06-04 17:17:33]

lgtm

[newt (away), 2013-06-04 17:37:03]

Committed patchset #1 manually as r203994 (presubmit successful).

[aurimas (slooooooooow), 2014-08-14 04:29:52]

On 2013/06/04 17:37:03, newt wrote:
> Committed patchset #1 manually as r203994 (presubmit successful).

Random question: why did we put these images under mipmap?

[Kibeom Kim (inactive), 2014-08-14 06:56:41]

On 2014/08/14 04:29:52, aurimas wrote:
> On 2013/06/04 17:37:03, newt wrote:
> > Committed patchset #1 manually as r203994 (presubmit successful).
> 
> Random question: why did we put these images under mipmap?

The question seriously challenges my memorization. :) I barely remember that it
was something to do with how Android deals launcher icons.

Random answer:
https://groups.google.com/d/msg/android-developers/ZUyF0JEwibs/5w3dC4aS0zsJ

[Kibeom Kim (inactive), 2014-08-14 07:54:01]

On 2014/08/14 06:56:41, Kibeom Kim wrote:
> On 2014/08/14 04:29:52, aurimas wrote:
> > On 2013/06/04 17:37:03, newt wrote:
> > > Committed patchset #1 manually as r203994 (presubmit successful).
> > 
> > Random question: why did we put these images under mipmap?
> 
> The question seriously challenges my memorization. :) I barely remember that
it
> was something to do with how Android deals launcher icons.
> 
> Random answer:
> https://groups.google.com/d/msg/android-developers/ZUyF0JEwibs/5w3dC4aS0zsJ

OK, I looked up where we're using this resource, BookmarkUtils.java, and it
seems mipmap-*/ doesn't make any difference in this case. I could be wrong of
course.

[Ted C, 2014-08-14 19:04:01]

On 2014/08/14 07:54:01, Kibeom Kim wrote:
> On 2014/08/14 06:56:41, Kibeom Kim wrote:
> > On 2014/08/14 04:29:52, aurimas wrote:
> > > On 2013/06/04 17:37:03, newt wrote:
> > > > Committed patchset #1 manually as r203994 (presubmit successful).
> > > 
> > > Random question: why did we put these images under mipmap?
> > 
> > The question seriously challenges my memorization. :) I barely remember that
> it
> > was something to do with how Android deals launcher icons.
> > 
> > Random answer:
> > https://groups.google.com/d/msg/android-developers/ZUyF0JEwibs/5w3dC4aS0zsJ
> 
> OK, I looked up where we're using this resource, BookmarkUtils.java, and it
> seems mipmap-*/ doesn't make any difference in this case. I could be wrong of
> course.

If I recall, mipmap is better for home screen assets as they can more correctly
use ones for the device/density without scaling artifacts of other resource
types (same reason we put our chrome icons in mipmap folders).

[Ted C, 2014-08-14 19:04:01]

On 2014/08/14 07:54:01, Kibeom Kim wrote:
> On 2014/08/14 06:56:41, Kibeom Kim wrote:
> > On 2014/08/14 04:29:52, aurimas wrote:
> > > On 2013/06/04 17:37:03, newt wrote:
> > > > Committed patchset #1 manually as r203994 (presubmit successful).
> > > 
> > > Random question: why did we put these images under mipmap?
> > 
> > The question seriously challenges my memorization. :) I barely remember that
> it
> > was something to do with how Android deals launcher icons.
> > 
> > Random answer:
> > https://groups.google.com/d/msg/android-developers/ZUyF0JEwibs/5w3dC4aS0zsJ
> 
> OK, I looked up where we're using this resource, BookmarkUtils.java, and it
> seems mipmap-*/ doesn't make any difference in this case. I could be wrong of
> course.

If I recall, mipmap is better for home screen assets as they can more correctly
use ones for the device/density without scaling artifacts of other resource
types (same reason we put our chrome icons in mipmap folders).

[Kibeom Kim (inactive), 2014-08-14 20:06:12]

On 2014/08/14 19:04:01, Ted C wrote:
> On 2014/08/14 07:54:01, Kibeom Kim wrote:
> > On 2014/08/14 06:56:41, Kibeom Kim wrote:
> > > On 2014/08/14 04:29:52, aurimas wrote:
> > > > On 2013/06/04 17:37:03, newt wrote:
> > > > > Committed patchset #1 manually as r203994 (presubmit successful).
> > > > 
> > > > Random question: why did we put these images under mipmap?
> > > 
> > > The question seriously challenges my memorization. :) I barely remember
that
> > it
> > > was something to do with how Android deals launcher icons.
> > > 
> > > Random answer:
> > >
https://groups.google.com/d/msg/android-developers/ZUyF0JEwibs/5w3dC4aS0zsJ
> > 
> > OK, I looked up where we're using this resource, BookmarkUtils.java, and it
> > seems mipmap-*/ doesn't make any difference in this case. I could be wrong
of
> > course.
> 
> If I recall, mipmap is better for home screen assets as they can more
correctly
> use ones for the device/density without scaling artifacts of other resource
> types (same reason we put our chrome icons in mipmap folders).

This is a simplified snippet how we're using the mipmap asset in
BookmarkUtils.java:

int iconDensity = (ActivityManager)
context.getSystemService(Context.ACTIVITY_SERVICE).getLauncherLargeIconSize();
Bitmap bookmarkWidgetBg = getBitmapFromResourceId(context,
R.mipmap.bookmark_widget_bg, iconDensity);
canvas.drawBitmap(bookmarkWidgetBg, null, iconBounds, paint);

So we just directly request the exact density asset first and convert it to
Bitmap. It doesn't seem any mipmap scaling is involved here.