cros: Use touch theme assets with --touch-optimized-ui

cros: Use touch theme assets with --touch-optimized-ui

This follows the same pattern for theme_resources_touch_1x as we used for ui_resources_touch.  I also introduced a gyp flag for enable_touch_ui at sky's suggestion.

BUG=115234
TEST=visual, run with --touch-optimized-ui and see bigger tabstrip and toolbar assets

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

[James Cook, 2012-05-02 15:44:41]

Sky, PTAL.

[sky, 2012-05-02 16:12:20]

http://codereview.chromium.org/10320002/diff/2001/build/common.gypi
File build/common.gypi (right):

http://codereview.chromium.org/10320002/diff/2001/build/common.gypi#newcode105
build/common.gypi:105: 'enable_touch_ui%': 1,
Are you sure you want to set this now for chromeos? Should we wait to
automatically set it until 20 branches?

[James Cook, 2012-05-02 16:22:20]

http://codereview.chromium.org/10320002/diff/2001/build/common.gypi
File build/common.gypi (right):

http://codereview.chromium.org/10320002/diff/2001/build/common.gypi#newcode105
build/common.gypi:105: 'enable_touch_ui%': 1,
On 2012/05/02 16:12:21, sky wrote:
> Are you sure you want to set this now for chromeos? Should we wait to
> automatically set it until 20 branches?

I think it's OK.  It only actually changes the visual appearance if you pass the
flag --touch-optimized-ui to ChromeOS Chrome.  Maybe I should change the name of
the flag to something like 'include_touch_assets'?

[sky, 2012-05-02 16:31:09]

On Wed, May 2, 2012 at 9:22 AM,  <jamescook@chromium.org> wrote:
>
> http://codereview.chromium.org/10320002/diff/2001/build/common.gypi
> File build/common.gypi (right):
>
>
http://codereview.chromium.org/10320002/diff/2001/build/common.gypi#newcode105
> build/common.gypi:105: 'enable_touch_ui%': 1,
> On 2012/05/02 16:12:21, sky wrote:
>>
>> Are you sure you want to set this now for chromeos? Should we wait to
>> automatically set it until 20 branches?
>
>
> I think it's OK.  It only actually changes the visual appearance if you
> pass the flag --touch-optimized-ui to ChromeOS Chrome.  Maybe I should
> change the name of the flag to something like 'include_touch_assets'?
>
> http://codereview.chromium.org/10320002/

Does it result in loading all the touch images?

  -Scott

[James Cook, 2012-05-02 16:34:59]

On 2012/05/02 16:31:09, sky wrote:
> On Wed, May 2, 2012 at 9:22 AM,  <mailto:jamescook@chromium.org> wrote:
> >
> > http://codereview.chromium.org/10320002/diff/2001/build/common.gypi
> > File build/common.gypi (right):
> >
> >
> http://codereview.chromium.org/10320002/diff/2001/build/common.gypi#newcode105
> > build/common.gypi:105: 'enable_touch_ui%': 1,
> > On 2012/05/02 16:12:21, sky wrote:
> >>
> >> Are you sure you want to set this now for chromeos? Should we wait to
> >> automatically set it until 20 branches?
> >
> >
> > I think it's OK. &nbsp;It only actually changes the visual appearance if you
> > pass the flag --touch-optimized-ui to ChromeOS Chrome. &nbsp;Maybe I should
> > change the name of the flag to something like 'include_touch_assets'?
> >
> > http://codereview.chromium.org/10320002/
> 
> Does it result in loading all the touch images?
> 
>   -Scott

It loads the touch images only if the --touch-optimized-ui flag is passed.

James

[sky, 2012-05-02 16:42:23]

Perfect, LGTM

[James Cook, 2012-05-02 20:02:49]

On 2012/05/02 16:42:23, sky wrote:
> Perfect, LGTM

Oops, did you mean perfect as-is or perfect assuming I rename the flag to
'include_touch_assets'?  I committed it with the name 'enable_touch_ui' - do you
think I should change it?

[sky, 2012-05-02 21:05:15]

Perfect as is.

On Wed, May 2, 2012 at 1:02 PM,  <jamescook@chromium.org> wrote:
> On 2012/05/02 16:42:23, sky wrote:
>>
>> Perfect, LGTM
>
>
> Oops, did you mean perfect as-is or perfect assuming I rename the flag to
> 'include_touch_assets'?  I committed it with the name 'enable_touch_ui' - do
> you
> think I should change it?
>
>
> http://codereview.chromium.org/10320002/