Add window manager component.

wm/host/foreign_test_window_host_linux.cc

+// Copyright (c) 2012 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 "wm/host/foreign_test_window_host_linux.h"
+
+#include "base/run_loop.h"
+#include "ui/aura/env.h"
+
+namespace wm {
+
+ForeignTestWindowHostLinux::ForeignTestWindowHostLinux(
+    gfx::AcceleratedWidget parent) : display_(NULL),

[danakj, 2013/02/21 01:33:15]

is this : on the same line thing legit style? never saw that before this cl

[reveman, 2013/02/22 01:26:44]

I like this when possible as it creates a nice separation between parameters and
the initializer list but maybe not legit so changing.. 

+                                     parent_(parent),
+                                     window_(0),
+                                     font_info_(NULL),
+                                     gc_(0) {
+}
+
+ForeignTestWindowHostLinux::~ForeignTestWindowHostLinux() {
+}
+
+void ForeignTestWindowHostLinux::Initialize() {
+  DCHECK(parent_);
+  display_ = XOpenDisplay(NULL);
+  size_ = gfx::Size(300, 300);
+  window_ = XCreateSimpleWindow(
+      display_,
+      parent_,
+      30, 30, size_.width(), size_.height(), 0,
+      BlackPixel(display_, DefaultScreen(display_)),
+      WhitePixel(display_, DefaultScreen(display_)));
+  XSelectInput(display_, window_, ExposureMask | StructureNotifyMask);
+  font_info_ = XLoadQueryFont(display_, "9x15");
+  DCHECK(font_info_);
+  gc_ = XCreateGC(display_, window_, 0, NULL);
+  XSetFont(display_, gc_, font_info_->fid);
+  XSetForeground(display_, gc_, BlackPixel(display_, DefaultScreen(display_)));
+
+  MessageLoopForIO::current()->WatchFileDescriptor(
+      ConnectionNumber(display_), true, MessageLoopForIO::WATCH_READ,
+      &connection_watcher_, this);
+
+  PumpXEvents();
+}
+
+void ForeignTestWindowHostLinux::Delete() {
+  connection_watcher_.StopWatchingFileDescriptor();
+  XFreeGC(display_, gc_);
+  XFreeFont(display_, font_info_);
+  XCloseDisplay(display_);
+  delete this;
+}
+
+void ForeignTestWindowHostLinux::Show() {
+  DCHECK(window_);
+  XMapWindow(display_, window_);
+}
+
+void ForeignTestWindowHostLinux::Hide() {
+  DCHECK(window_);
+  XUnmapWindow(display_, window_);
+}
+
+void ForeignTestWindowHostLinux::Destroy() {
+  XDestroyWindow(display_, window_);
+  window_ = 0;
+}
+
+void ForeignTestWindowHostLinux::Sync() {
+  XSync(display_, False);
+}
+
+void ForeignTestWindowHostLinux::ProcessXEvent(XEvent *event) {
+  switch (event->type) {
+    case Expose: {
+      if (event->xexpose.count != 0)
+        break;
+
+      std::string message("Hello, X Window System!");
+
+      // Center text.
+      int width = XTextWidth(font_info_, message.c_str(), message.length());
+      int msg_x  = (size_.width() - width) / 2;
+
+      int font_height = font_info_->ascent + font_info_->descent;
+      int msg_y  = (size_.height() + font_height) / 2;
+
+      XDrawString(display_,
+                  window_,
+                  gc_,
+                  msg_x, msg_y,
+                  message.c_str(), message.length());
+    } break;
+    case ConfigureNotify: {
+      size_ = gfx::Size(event->xconfigure.width, event->xconfigure.height);
+    } break;
+  }
+}
+
+void ForeignTestWindowHostLinux::PumpXEvents() {
+  while (XPending(display_)) {
+    XEvent event;
+    XNextEvent(display_, &event);
+    ProcessXEvent(&event);
+  }
+}
+
+void ForeignTestWindowHostLinux::OnFileCanReadWithoutBlocking(int fd) {
+  PumpXEvents();
+}
+
+void ForeignTestWindowHostLinux::OnFileCanWriteWithoutBlocking(int fd) {
+}
+
+// static
+ForeignTestWindowHost* ForeignTestWindowHost::Create(
+    gfx::AcceleratedWidget parent) {

[danakj, 2013/02/21 01:33:15]

Why is an X window sometimes AcceleratedWidget and sometimes
PluginWindowThinger?

[reveman, 2013/02/22 01:26:44]

RootWindowHost uses AcceleratedWidget and BrowserGpuChannelHostFactory uses
gfx::PluginWindowHandle. Platform specific code is needed to bridge these.

[danakj, 2013/02/22 01:48:08]

Oh argh. Do you think BGCHF could use AcceleratedWidget in the future, or is it
incompatible on some platforms?

[reveman, 2013/02/22 06:53:01]

I tried that initially when adding CHROMIUM_texture_from_image but it requires
platform specific code on the browser side and is not very pretty. Handling this
in wm::ForeignTestWindowHostLinux and wm::RootWindowHostLinux is much better. 

We could always use aura::RootWindow* here instead of gfx::AcceleratedWidget..

[danakj, 2013/02/22 21:42:59]

I think I would prefer that. Keeping the AcceleratedWidget stuff as contained as
possible seems positive.

+  return new ForeignTestWindowHostLinux(parent);
+}
+
+// static
+void ForeignTestWindowHost::RunAllPendingInMessageLoop() {
+  Display* display = base::MessagePumpAuraX11::GetDefaultXDisplay();
+  XSync(display, False);
+  base::RunLoop run_loop(aura::Env::GetInstance()->GetDispatcher());
+  run_loop.RunUntilIdle();
+}
+
+}  // namespace wm