Move ui::gfx::Image out of the ui namespace to be just gfx::Image.

Move ui::gfx::Image out of the ui namespace to be just gfx::Image.

Having namespaces ui::gfx and just gfx are causing compiler disambiguation
problems. This will resolve that.

BUG=carnitas
TEST=compiles and gfx_unittests

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=75283

[Mark Mentovai, 2011-02-17 00:38:26]

Isn’t this contrary to the new namespacing policy?

Where is this causing trouble? Would fully qualifying things with a leading ::
help?

[Robert Sesek, 2011-02-17 01:26:47]

On Wed, Feb 16, 2011 at 7:38 PM, <mark@chromium.org> wrote:

> Isn’t this contrary to the new namespacing policy?
>
> Where is this causing trouble? Would fully qualifying things with a leading
> ::
> help?


Currently everything in /ui/gfx is still in just the gfx namespace, and has
not yet been wrapped in the ui namespace. I talked to Ben about this, and he
doesn't like ui::gfx; additionally the /ui directory is still in flux, so
things may continue to be renamed. At the same time, I'd like to move
forward with my little subproject and integrating this into ResourceBundle
gets very ugly when I have to prefix all the other members with ::gfx, of
which there are a lot. It's easiest to just conform until the naming is
settled and changed all at once.

rsesek / @chromium.org


> http://codereview.chromium.org/6533013/
>

[Mark Mentovai, 2011-02-17 17:20:36]

OK, looks good.