Renamed .pak and .rc files

Renamed resource files to be more verbose, specifically:
ui_resources_standard.pak => ui_resources_100_percent.pak
ui_resources_2x.pak => ui_resources_200_percent.pak
ui_resources_standard.rc => ui_resources_100_percent.rc
theme_resources_standard.pak => theme_resources_100_percent.pak
theme_resources_2x.pak => theme_resources_200_percent.pak
theme_resources_standard.rc => theme_resources_100_percent.rc

BUG=120185
TEST=run chome,ash_shell confirm assets loaded

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

[Harry McCleave, 2012-07-12 22:27:57]

Please take a look.

[sail, 2012-07-12 22:36:42]

Thanks for doing this!
+benrg who's also updating the resource pak files.

https://chromiumcodereview.appspot.com/10694170/diff/1/ash/ash.gyp
File ash/ash.gyp (right):

https://chromiumcodereview.appspot.com/10694170/diff/1/ash/ash.gyp#newcode451
ash/ash.gyp:451: '<(SHARED_INTERMEDIATE_DIR)/ui/ui_resources/ui_resources.rc',
should this be ui_resources_100.rc?

https://chromiumcodereview.appspot.com/10694170/diff/1/chrome/app/theme/theme...
File chrome/app/theme/theme_resources.grd (right):

https://chromiumcodereview.appspot.com/10694170/diff/1/chrome/app/theme/theme...
chrome/app/theme/theme_resources.grd:13: <output filename="theme_resources.rc"
type="rc_all" context="default_100_percent" />
theme_resources_100.rc?

[benrg, 2012-07-12 22:51:08]

LGTM with the RC files renamed.

https://chromiumcodereview.appspot.com/10694170/diff/1/ash/ash.gyp
File ash/ash.gyp (right):

https://chromiumcodereview.appspot.com/10694170/diff/1/ash/ash.gyp#newcode451
ash/ash.gyp:451: '<(SHARED_INTERMEDIATE_DIR)/ui/ui_resources/ui_resources.rc',
On 2012/07/12 22:36:43, sail wrote:
> should this be ui_resources_100.rc?

Yes, the unscaled outputs have context="..." on them because of a Grit
bug/limitation, but the rc files really are scaled and should have 100_percent
in the name.

[grt (UTC plus 2), 2012-07-16 07:29:13]

rubber-stamp lgtm for chrome_frame

[commit-bot: I haz the power, 2012-07-16 20:56:26]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/harrym@chromium.org/10694170/3004

[commit-bot: I haz the power, 2012-07-16 20:56:32]

Presubmit check for 10694170-3004 failed and returned exit status 1.

Running presubmit commit checks ...

** Presubmit Warnings **
Found lines longer than 80 characters (first 5 shown).
  ui/base/resource/resource_bundle_android.cc, line 34, 81 chars \
  ui/base/resource/resource_bundle_aurax11.cc, line 47, 89 chars \
  ui/base/resource/resource_bundle_aurax11.cc, line 49, 86 chars \
  ui/base/resource/resource_bundle_aurax11.cc, line 56, 88 chars \
  ui/base/resource/resource_bundle_aurax11.cc, line 61, 83 chars

** Presubmit ERRORS **
Missing LGTM from an OWNER for files in these directories:
    ui/aura
    content
    ui/compositor
    ui
    ui/base/resource
    webkit
    ui/views
    ash
    ui/resources

[commit-bot: I haz the power, 2012-07-16 20:57:06]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/harrym@chromium.org/10694170/3004

[commit-bot: I haz the power, 2012-07-16 20:57:19]

Presubmit check for 10694170-3004 failed and returned exit status 1.

Running presubmit commit checks ...

** Presubmit Warnings **
Found lines longer than 80 characters (first 5 shown).
  ui/base/resource/resource_bundle_android.cc, line 34, 81 chars \
  ui/base/resource/resource_bundle_aurax11.cc, line 47, 89 chars \
  ui/base/resource/resource_bundle_aurax11.cc, line 49, 86 chars \
  ui/base/resource/resource_bundle_aurax11.cc, line 56, 88 chars \
  ui/base/resource/resource_bundle_aurax11.cc, line 61, 83 chars

** Presubmit ERRORS **
Missing LGTM from an OWNER for files in these directories:
    ui/aura
    content
    ui/compositor
    ui
    ui/base/resource
    webkit
    ui/views
    ash
    ui/resources

[sail, 2012-07-17 14:05:43]

Hi Harry, is this ready for another look? If so please reply to the CL comments
above and ask for another look. Also, please wait for an ok from all reviewers
before committing.

[sail, 2012-07-17 14:06:42]

Also, please expand the CL description to explicitly list all the files that
have changed. This is really helpful later. Thanks.

[Harry McCleave, 2012-07-17 22:09:56]

On 2012/07/17 14:06:42, sail wrote:
> Also, please expand the CL description to explicitly list all the files that
> have changed. This is really helpful later. Thanks.

The change should be ready for a look.

[sail, 2012-07-17 22:24:51]

On 2012/07/17 22:09:56, Harry McCleave wrote:
> On 2012/07/17 14:06:42, sail wrote:
> > Also, please expand the CL description to explicitly list all the files that
> > have changed. This is really helpful later. Thanks.
> 
> The change should be ready for a look.

Could you address each of the above comments. It's typical to press reply on
each of the above comments and say "Done" or provide an explanation. This makes
the review process faster and it's easier to spot things that didn't get
addressed.

[Harry McCleave, 2012-07-18 01:03:05]

On 2012/07/12 22:51:08, benrg wrote:
> LGTM with the RC files renamed.
> 
> https://chromiumcodereview.appspot.com/10694170/diff/1/ash/ash.gyp
> File ash/ash.gyp (right):
> 
> https://chromiumcodereview.appspot.com/10694170/diff/1/ash/ash.gyp#newcode451
> ash/ash.gyp:451: '<(SHARED_INTERMEDIATE_DIR)/ui/ui_resources/ui_resources.rc',
> On 2012/07/12 22:36:43, sail wrote:
> > should this be ui_resources_100.rc?
> 
> Yes, the unscaled outputs have context="..." on them because of a Grit
> bug/limitation, but the rc files really are scaled and should have 100_percent
> in the name.

Please take a look at updated change when you get a chance thanks.

[Harry McCleave, 2012-07-18 01:03:22]

On 2012/07/16 07:29:13, grt wrote:
> rubber-stamp lgtm for chrome_frame

Please take a look at updated change when you get a chance thanks.

[sail, 2012-07-18 01:15:12]

LGTM!

[darin (slow to review), 2012-07-18 06:03:40]

LGTM

[sky, 2012-07-18 14:54:33]

LGTM

[commit-bot: I haz the power, 2012-07-18 18:07:05]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/harrym@chromium.org/10694170/18002

[commit-bot: I haz the power, 2012-07-18 19:13:11]

Change committed as 147288

[Harry McCleave, 2012-07-23 20:29:47]

On 2012/07/18 19:13:11, I haz the power (commit-bot) wrote:
> Change committed as 147288

Change has been updated to fix some missed references and rebase the code,
please take a look if you wish to re-review, or let me know if its ok to attempt
another launch.

[sail, 2012-07-23 20:34:38]

On 2012/07/23 20:29:47, Harry McCleave wrote:
> On 2012/07/18 19:13:11, I haz the power (commit-bot) wrote:
> > Change committed as 147288
> 
> Change has been updated to fix some missed references and rebase the code,
> please take a look if you wish to re-review, or let me know if its ok to
attempt
> another launch.

Did the old change get reverted? If not is this a new CL?

[Harry McCleave, 2012-07-23 20:39:10]

On 2012/07/23 20:34:38, sail wrote:
> On 2012/07/23 20:29:47, Harry McCleave wrote:
> > On 2012/07/18 19:13:11, I haz the power (commit-bot) wrote:
> > > Change committed as 147288
> > 
> > Change has been updated to fix some missed references and rebase the code,
> > please take a look if you wish to re-review, or let me know if its ok to
> attempt
> > another launch.
> 
> Did the old change get reverted? If not is this a new CL?

Yup, old change got reverted.

[sail, 2012-07-23 20:47:47]

On 2012/07/23 20:39:10, Harry McCleave wrote:
> On 2012/07/23 20:34:38, sail wrote:
> > On 2012/07/23 20:29:47, Harry McCleave wrote:
> > > On 2012/07/18 19:13:11, I haz the power (commit-bot) wrote:
> > > > Change committed as 147288
> > > 
> > > Change has been updated to fix some missed references and rebase the code,
> > > please take a look if you wish to re-review, or let me know if its ok to
> > attempt
> > > another launch.
> > 
> > Did the old change get reverted? If not is this a new CL?
> 
> Yup, old change got reverted.

Ahh, could you make the change I asked for last time (update the CL with files
names fully spelled out)?

[Harry McCleave, 2012-07-23 20:52:10]

On 2012/07/23 20:47:47, sail wrote:
> On 2012/07/23 20:39:10, Harry McCleave wrote:
> > On 2012/07/23 20:34:38, sail wrote:
> > > On 2012/07/23 20:29:47, Harry McCleave wrote:
> > > > On 2012/07/18 19:13:11, I haz the power (commit-bot) wrote:
> > > > > Change committed as 147288
> > > > 
> > > > Change has been updated to fix some missed references and rebase the
code,
> > > > please take a look if you wish to re-review, or let me know if its ok to
> > > attempt
> > > > another launch.
> > > 
> > > Did the old change get reverted? If not is this a new CL?
> > 
> > Yup, old change got reverted.
> 
> Ahh, could you make the change I asked for last time (update the CL with files
> names fully spelled out)?

Done

[sail, 2012-07-23 20:55:29]

On 2012/07/23 20:52:10, Harry McCleave wrote:
> On 2012/07/23 20:47:47, sail wrote:
> > On 2012/07/23 20:39:10, Harry McCleave wrote:
> > > On 2012/07/23 20:34:38, sail wrote:
> > > > On 2012/07/23 20:29:47, Harry McCleave wrote:
> > > > > On 2012/07/18 19:13:11, I haz the power (commit-bot) wrote:
> > > > > > Change committed as 147288
> > > > > 
> > > > > Change has been updated to fix some missed references and rebase the
> code,
> > > > > please take a look if you wish to re-review, or let me know if its ok
to
> > > > attempt
> > > > > another launch.
> > > > 
> > > > Did the old change get reverted? If not is this a new CL?
> > > 
> > > Yup, old change got reverted.
> > 
> > Ahh, could you make the change I asked for last time (update the CL with
files
> > names fully spelled out)?
> 
> Done

This new code doesn't have any GYP/GRD changes from the original patch. That
doesn't seem right.

[Harry McCleave, 2012-07-23 20:57:57]

On 2012/07/23 20:55:29, sail wrote:
> On 2012/07/23 20:52:10, Harry McCleave wrote:
> > On 2012/07/23 20:47:47, sail wrote:
> > > On 2012/07/23 20:39:10, Harry McCleave wrote:
> > > > On 2012/07/23 20:34:38, sail wrote:
> > > > > On 2012/07/23 20:29:47, Harry McCleave wrote:
> > > > > > On 2012/07/18 19:13:11, I haz the power (commit-bot) wrote:
> > > > > > > Change committed as 147288
> > > > > > 
> > > > > > Change has been updated to fix some missed references and rebase the
> > code,
> > > > > > please take a look if you wish to re-review, or let me know if its
ok
> to
> > > > > attempt
> > > > > > another launch.
> > > > > 
> > > > > Did the old change get reverted? If not is this a new CL?
> > > > 
> > > > Yup, old change got reverted.
> > > 
> > > Ahh, could you make the change I asked for last time (update the CL with
> files
> > > names fully spelled out)?
> > 
> > Done
> 
> This new code doesn't have any GYP/GRD changes from the original patch. That
> doesn't seem right.

Are they not included? I thought it only showed the files that changed in the
current patch? (but would commit the whole lot of it, though as I am new here
quite possible I am mistaken about this)

[sail, 2012-07-23 21:05:21]

On 2012/07/23 20:57:57, Harry McCleave wrote:
> On 2012/07/23 20:55:29, sail wrote:
> > On 2012/07/23 20:52:10, Harry McCleave wrote:
> > > On 2012/07/23 20:47:47, sail wrote:
> > > > On 2012/07/23 20:39:10, Harry McCleave wrote:
> > > > > On 2012/07/23 20:34:38, sail wrote:
> > > > > > On 2012/07/23 20:29:47, Harry McCleave wrote:
> > > > > > > On 2012/07/18 19:13:11, I haz the power (commit-bot) wrote:
> > > > > > > > Change committed as 147288
> > > > > > > 
> > > > > > > Change has been updated to fix some missed references and rebase
the
> > > code,
> > > > > > > please take a look if you wish to re-review, or let me know if its
> ok
> > to
> > > > > > attempt
> > > > > > > another launch.
> > > > > > 
> > > > > > Did the old change get reverted? If not is this a new CL?
> > > > > 
> > > > > Yup, old change got reverted.
> > > > 
> > > > Ahh, could you make the change I asked for last time (update the CL with
> > files
> > > > names fully spelled out)?
> > > 
> > > Done
> > 
> > This new code doesn't have any GYP/GRD changes from the original patch. That
> > doesn't seem right.
> 
> Are they not included? I thought it only showed the files that changed in the
> current patch? (but would commit the whole lot of it, though as I am new here
> quite possible I am mistaken about this)

No it's not included. You need to upload a single diff for the whole change.

[Harry McCleave, 2012-07-23 21:28:21]

On 2012/07/23 21:05:21, sail wrote:
> On 2012/07/23 20:57:57, Harry McCleave wrote:
> > On 2012/07/23 20:55:29, sail wrote:
> > > On 2012/07/23 20:52:10, Harry McCleave wrote:
> > > > On 2012/07/23 20:47:47, sail wrote:
> > > > > On 2012/07/23 20:39:10, Harry McCleave wrote:
> > > > > > On 2012/07/23 20:34:38, sail wrote:
> > > > > > > On 2012/07/23 20:29:47, Harry McCleave wrote:
> > > > > > > > On 2012/07/18 19:13:11, I haz the power (commit-bot) wrote:
> > > > > > > > > Change committed as 147288
> > > > > > > > 
> > > > > > > > Change has been updated to fix some missed references and rebase
> the
> > > > code,
> > > > > > > > please take a look if you wish to re-review, or let me know if
its
> > ok
> > > to
> > > > > > > attempt
> > > > > > > > another launch.
> > > > > > > 
> > > > > > > Did the old change get reverted? If not is this a new CL?
> > > > > > 
> > > > > > Yup, old change got reverted.
> > > > > 
> > > > > Ahh, could you make the change I asked for last time (update the CL
with
> > > files
> > > > > names fully spelled out)?
> > > > 
> > > > Done
> > > 
> > > This new code doesn't have any GYP/GRD changes from the original patch.
That
> > > doesn't seem right.
> > 
> > Are they not included? I thought it only showed the files that changed in
the
> > current patch? (but would commit the whole lot of it, though as I am new
here
> > quite possible I am mistaken about this)
> 
> No it's not included. You need to upload a single diff for the whole change.

Done

[sail, 2012-07-23 21:42:07]

LGTM!

[commit-bot: I haz the power, 2012-07-23 22:22:57]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/harrym@chromium.org/10694170/32004

[commit-bot: I haz the power, 2012-07-23 22:23:16]

Presubmit check for 10694170-32004 failed and returned exit status 1.

Running presubmit commit checks ...

** Presubmit Warnings **
Found lines longer than 80 characters (first 5 shown).
  ui/base/resource/resource_bundle_mac.mm, line 54, 83 chars \
  ui/base/resource/resource_bundle_mac.mm, line 63, 85 chars \
  ui/base/resource/resource_bundle_mac.mm, line 65, 82 chars

Presubmit checks took 2.3s to calculate.

[commit-bot: I haz the power, 2012-07-23 22:38:30]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/harrym@chromium.org/10694170/38003

[commit-bot: I haz the power, 2012-07-23 22:38:53]

Presubmit check for 10694170-38003 failed and returned exit status 1.

Running presubmit commit checks ...

** Presubmit Warnings **
Found line ending with white spaces in:

***************
ui/base/resource/resource_bundle_mac.mm, line 56
***************

Presubmit checks took 5.7s to calculate.

[commit-bot: I haz the power, 2012-07-23 23:22:56]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/harrym@chromium.org/10694170/26004

[commit-bot: I haz the power, 2012-07-24 00:55:44]

Try job failure for 10694170-26004 (retry) on mac_rel for step "browser_tests".
It's a second try, previously, step "browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_rel&nu...

[commit-bot: I haz the power, 2012-07-24 17:23:53]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/harrym@chromium.org/10694170/26004

[commit-bot: I haz the power, 2012-07-24 18:39:33]

Try job failure for 10694170-26004 (retry) on mac_rel for step "browser_tests".
It's a second try, previously, step "browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_rel&nu...

[commit-bot: I haz the power, 2012-07-24 20:32:23]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/harrym@chromium.org/10694170/26004

[commit-bot: I haz the power, 2012-07-24 21:52:06]

Try job failure for 10694170-26004 (retry) on mac_rel for step "browser_tests".
It's a second try, previously, step "browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_rel&nu...

[Emmanuel Saint-loubert-Bié, 2012-07-24 22:13:48]

lgtm

LGTM will land by hand, since CQ us not cooperating.

[commit-bot: I haz the power, 2012-07-24 22:15:03]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/harrym@chromium.org/10694170/26004