Move scoped_nsdisable_screen_update from base to app/mac...

Move scoped_nsdisable_screen_update from base to app/mac
Move scoped_aedesc from base to base/mac
Use namespace and proper Google-style class naming.

TEST=it compiles
BUG=none

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

[brettw, 2010-10-18 02:44:55]

TBR

[Scott Hess - ex-Googler, 2010-10-18 13:24:30]

LGTM for moving the specific files around.

I think that base::mac:: namespace veers towards Hungarian notation in terms of
pedantry, since the vast majority of uses are in mac-specific code anyhow.  Do
we really need to go there?

[brettw, 2010-10-18 15:53:21]

On Mon, Oct 18, 2010 at 6:24 AM,  <shess@chromium.org> wrote:
> LGTM for moving the specific files around.
>
> I think that base::mac:: namespace veers towards Hungarian notation in terms
> of
> pedantry, since the vast majority of uses are in mac-specific code anyhow.
>  Do
> we really need to go there?

Yeah, I kind of agree. There are definitely some cases where it helps.
ScopedNSAutoreleasePool is nice because it's actually used on other
platforms (as a NOP) and seeing the mac namespace there I think is
helpful in seeing what it's for. There were a couple of classes on the
Windows side that it helped as well. Plus, I'm hoping to kill all the
mac/win/etc_util.h files and put them in the platform directories with
actually descriptive filenames for what they are. I plan to just use
free-floating functions in the base::*:: namespace rather than
win_util::.

In the end, I'm hoping that being consistent with the naming,
directory structure, and namespace will pay off overall even though
there will be a few common cases that look stupid.

Brett