Implement OzonePlatform

ui/base/ozone/ozone_platform.cc

Index: ui/base/ozone/ozone_platform.cc
diff --git a/ui/base/ozone/ozone_platform.cc b/ui/base/ozone/ozone_platform.cc
new file mode 100644
index 0000000000000000000000000000000000000000..ea638c24719b2ee256cbe9829feeb3e28b6f4fbb
--- /dev/null
+++ b/ui/base/ozone/ozone_platform.cc
@@ -0,0 +1,28 @@
+// Copyright (c) 2013 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.
+
+#include "base/command_line.h"
+#include "base/logging.h"
+#include "ui/base/ozone/ozone_platform.h"
+
+namespace ui {
+
+OzonePlatform::OzonePlatform() {}
+
+OzonePlatform::~OzonePlatform() {
+  gfx::SurfaceFactoryOzone::SetInstance(NULL);
+  ui::EventFactoryOzone::SetInstance(NULL);
+}
+
+// static
+OzonePlatform* OzonePlatform::Create() {
+  OzonePlatform* platform = CreateDefaultOzonePlatform();
+
+  gfx::SurfaceFactoryOzone::SetInstance(platform->GetSurfaceFactoryOzone());
+  ui::EventFactoryOzone::SetInstance(platform->GetEventFactoryOzone());
+

[vignatti (out of this project), 2013/10/28 15:26:44]

In the description you mention that it "depends on code in 
ui/gfx and ui/events because it must inject implementations into those
components". So, it's worth to mention that it depends on views as well
(ui/views/) for desktop aura cases and therefore some platforms want to
implement DesktopFactoryOzone.

That said, we probably want to add here the ::SetInstance on
views::DesktopFactoryOzone as well.

[spang, 2013/10/28 15:42:30]

We can't actually add a dependency from ui/base to views as this is against the
layering rules. We discussed this exact issue yesterday and we think we should
instead kill DesktopFactoryOzone and provide a different abstraction in ui/base
(I think sadrul suggested calling it PlatformWindow or something like that).

In the meantime, you'll have to workaround and inject DFO yourself.

[vignatti (out of this project), 2013/10/28 16:08:50]

ok, I see.

I'm very interested then to hear what's sadrul@ ideas cause otherwise the
solution you're proposing doesn't solve the main problem and desktop aura
targets will still have to inject platform specific code in Chromium. Please let
me know your plans on this.

+  return platform;
+}
+
+}  // namespace ui