Desktop aura: Continue threading context through views.

ui/views/test/views_test_base.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 "ui/views/test/views_test_base.h"
 
 #include "base/run_loop.h"
 #include "ui/base/clipboard/clipboard.h"
 
 #if defined(USE_AURA)
 #include "ui/aura/env.h"
+#include "ui/aura/root_window.h"
 #include "ui/aura/test/aura_test_helper.h"
 #endif
 
 namespace views {
 
 ViewsTestBase::ViewsTestBase()
     : setup_called_(false),
       teardown_called_(false) {
 }
 
@@ skipping 30 matching lines @@
 }
 
 void ViewsTestBase::RunPendingMessages() {
   base::RunLoop run_loop;
 #if defined(USE_AURA)
   run_loop.set_dispatcher(aura::Env::GetInstance()->GetDispatcher());
 #endif
   run_loop.RunUntilIdle();
 }
 
+Widget::InitParams ViewsTestBase::CreateParams(
+    Widget::InitParams::Type type) {

[Ben Goodger (Google), 2012/11/29 22:16:20]

rather than adding this method, can you instead have this class tell the
TestViewsDelegate the context and have it implement CreateNativeWidget()?

[Elliot Glaysher, 2012/11/29 22:46:29]

That's moving where the global state is. I'd like it gone.

So currently, scottmg made it so that a context window is passed around as part
of the InitParams and I think this is the right design choice: the widget
creator is who has the information about where the widget should be created. I
eventually want to add a CHECK to NativeWidgetAura::InitParams to ensure that
either a parent, parent_widget or context has been given because we need some
handle to a aura::RootWindow.

Modifying the TestViewsDelegate, so that it is created on each test and creates
a special NativeWidgetAura, doesn't feel correct because it would be another
divergence from what's being tested since additional data usually isn't passed
in to NativeWidget subclasses at construction time. (I suppose we could move the
context to the NativeWidgetDelegate, but that doesn't seem strictly better.)

We could modify the ViewsDelegate::CreateNativeWidget() interface so that it
also took a context parameter, but that feels more like threading aura specific
context through cross platform code than the way I did it, where everything aura
specific has been centralized here.

+  Widget::InitParams params(type);
+  params.ownership = views::Widget::InitParams::WIDGET_OWNS_NATIVE_WIDGET;
+#if defined(USE_AURA)
+  params.context = aura_test_helper_->root_window();
+#endif
+  return params;
+}
+
 }  // namespace views