Add a basic linux client for Blimp.

blimp/client/linux/blimp_display_manager.cc

+// Copyright 2015 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 "blimp/client/linux/blimp_display_manager.h"
+
+#include "blimp/client/compositor/blimp_compositor.h"
+#include "blimp/client/session/render_widget_feature.h"
+#include "blimp/client/session/tab_control_feature.h"
+#include "ui/events/event.h"
+#include "ui/gfx/geometry/size.h"
+#include "ui/platform_window/platform_window.h"
+#include "ui/platform_window/x11/x11_window.h"
+
+namespace blimp {
+
+BlimpDisplayManager::BlimpDisplayManager(
+    const gfx::Size& window_size,
+    BlimpDisplayManagerDelegate* delegate,
+    RenderWidgetFeature* render_widget_feature,
+    TabControlFeature* tab_control_feature)
+    : device_pixel_ratio_(1.f),
+      delegate_(delegate),
+      tab_control_feature_(tab_control_feature),
+      blimp_compositor_(new BlimpCompositor(1.f, render_widget_feature)),
+      platform_window_(new ui::X11Window(this)) {
+  platform_window_->SetBounds(gfx::Rect(window_size));
+  platform_window_->Show();

[Wez, 2016/01/05 19:15:02]

nit: Do we want to show the platform window _before_ we finish setting the
compositor size, etc?  Won't that mean that we get a blank window that then has
some flickery stuff happen in it at startup?

+  blimp_compositor_->SetSize(window_size);
+  tab_control_feature_->SetSizeAndScale(platform_window_->GetBounds().size(),
+                                        device_pixel_ratio_);
+
+  blimp_compositor_->SetVisible(true);
+}
+
+BlimpDisplayManager::~BlimpDisplayManager() {}
+
+void BlimpDisplayManager::OnBoundsChanged(const gfx::Rect& new_bounds) {
+  blimp_compositor_->SetSize(new_bounds.size());
+  tab_control_feature_->SetSizeAndScale(new_bounds.size(), device_pixel_ratio_);
+}
+
+void BlimpDisplayManager::OnDamageRect(const gfx::Rect& damaged_region) {}

[Wez, 2016/01/05 19:15:02]

Doesn't damage need to be passed to the compositor to trigger re-rendering?

+
+void BlimpDisplayManager::DispatchEvent(ui::Event* event) {
+  // TODO(dtrainor): Look into using web_input_event_aura to translate these to
+  // blink events.
+}
+
+void BlimpDisplayManager::OnCloseRequest() {
+  blimp_compositor_->SetVisible(false);
+  platform_window_->Close();
+}
+
+void BlimpDisplayManager::OnClosed() {
+  if (delegate_)
+    delegate_->OnClosed();

[Wez, 2016/01/05 19:15:02]

We could almost just exit the process directly in this case, and wire up proper
teardown later, if we want.

+}
+
+void BlimpDisplayManager::OnWindowStateChanged(
+    ui::PlatformWindowState new_state) {}
+
+void BlimpDisplayManager::OnLostCapture() {}
+
+void BlimpDisplayManager::OnAcceleratedWidgetAvailable(
+    gfx::AcceleratedWidget widget,
+    float device_pixel_ratio) {
+  device_pixel_ratio_ = device_pixel_ratio;
+  tab_control_feature_->SetSizeAndScale(platform_window_->GetBounds().size(),
+                                        device_pixel_ratio_);
+
+  if (widget != gfx::kNullAcceleratedWidget)
+    blimp_compositor_->SetAcceleratedWidget(widget);

[Wez, 2016/01/05 19:15:02]

If the widget has become kNullAcceleratedWidget then don't we need to do
anything to stop the compositor from potentially touching the old, presumably
now invalid, widget?

+}
+
+void BlimpDisplayManager::OnAcceleratedWidgetDestroyed() {
+  blimp_compositor_->ReleaseAcceleratedWidget();
+}
+
+void BlimpDisplayManager::OnActivationChanged(bool active) {}
+
+}  // namespace blimp