[MD] Implement incognito colors as a NativeTheme (for Aura).

ui/native_theme/BUILD.gn

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 import("//build/config/ui.gni")
 
 component("native_theme") {
   sources = [
     "common_theme.cc",
     "common_theme.h",
@@ skipping 10 matching lines @@
     "native_theme_switches.cc",
     "native_theme_switches.h",
     "native_theme_win.cc",
     "native_theme_win.h",
   ]
 
   if (use_aura) {
     sources += [
       "native_theme_aura.cc",
       "native_theme_aura.h",
+      "native_theme_aura_dark.cc",
+      "native_theme_aura_dark.h",
     ]
 
     if (is_win) {
       sources += [
         "native_theme_aurawin.cc",
         "native_theme_aurawin.h",
       ]
     }
   }
 
+  if (is_win) {
+    sources += [
+      "native_theme_win_dark.cc",

[sky, 2015/11/12 21:58:28]

Generally platform specific files end with the platform, eg
native_theme_dark_win. Is there a reason not to do that here?

[Evan Stade, 2015/11/12 22:11:11]

Here is the inheritance chain:

NativeTheme : NativeThemeWin : NativeThemeWinDark

I wanted to add additional specializations on to the end rather than putting
them in the middle. But otherwise no, there's no particular reason
NativeThemeDarkWin wouldn't work.

[sky, 2015/11/12 23:45:52]

I'm not suggesting moving any code, just the name. And I get what you're saying,
but I think Win is the end is generally how we name things like this and works
better with build stuff.

[Evan Stade, 2015/11/13 18:11:40]

changed the name

+      "native_theme_win_dark.h",
+    ]
+  }
+
   defines = [ "NATIVE_THEME_IMPLEMENTATION" ]
 
   deps = [
     "//base",
     "//base/third_party/dynamic_annotations",
     "//skia",
     "//ui/base",
     "//ui/gfx",
     "//ui/gfx/geometry",
     "//ui/resources",
   ]
 }