Add helpers for creating UI components.

mojo/ui/base_view.h

Index: mojo/ui/base_view.h
diff --git a/mojo/ui/base_view.h b/mojo/ui/base_view.h
new file mode 100644
index 0000000000000000000000000000000000000000..439724dd6396f1d817b0e1266bbdd8b97158b561
--- /dev/null
+++ b/mojo/ui/base_view.h
@@ -0,0 +1,79 @@
+// 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.
+
+#ifndef MOJO_UI_BASE_VIEW_H_
+#define MOJO_UI_BASE_VIEW_H_
+
+#include <string>
+
+#include "mojo/public/cpp/application/application_impl.h"
+#include "mojo/public/cpp/bindings/strong_binding.h"
+#include "mojo/public/cpp/system/macros.h"
+#include "mojo/public/interfaces/application/service_provider.mojom.h"
+#include "mojo/services/gfx/composition/interfaces/scenes.mojom.h"
+#include "mojo/services/ui/views/interfaces/view_manager.mojom.h"
+#include "mojo/services/ui/views/interfaces/view_provider.mojom.h"
+#include "mojo/services/ui/views/interfaces/views.mojom.h"
+
+namespace mojo {
+namespace ui {
+
+// Abstract base implementation of the View interface for simple applications.
+// Subclasses must handle layout and provide content for the scene.

[viettrungluu, 2016/01/05 21:35:17]

It'd be nice to have a comment (maybe in the class itself) indicating exactly
what method needs to be implemented.

Ditto for GaneshView (whence I came).

(I really got here from reading examples::ShapesView. Admittedly, such comments
would be fragile, but having to chase things up the class hierarchy is a bit
annoying.)

[jeffbrown, 2016/01/26 07:25:15]

The View mojom is going to change shortly so for now I'll just add a comment
saying go look there.

+//
+// It is not necessary to use this class to implement all Views.
+// This class is merely intended to make the simple apps easier to write.
+class BaseView : public mojo::ui::View {
+ public:
+  // TODO(jeffbrown): Consider switching this over to an ApplicationConnector
+  // but having ApplicationImpl is handy for simple examples.
+  BaseView(
+      mojo::ApplicationImpl* app_impl,
+      const std::string& label,
+      const mojo::ui::ViewProvider::CreateViewCallback& create_view_callback);
+
+  ~BaseView() override;
+
+  // Gets the application implementation object provided at creation time.
+  mojo::ApplicationImpl* app_impl() { return app_impl_; }
+
+  // Gets the view manager.
+  mojo::ui::ViewManager* view_manager() { return view_manager_.get(); }
+
+  // Gets the view host for the view.
+  mojo::ui::ViewHost* view_host() { return view_host_.get(); }
+
+  // Gets the service provider for the view.
+  mojo::ServiceProvider* view_service_provider() {
+    return view_service_provider_.get();
+  }
+
+  // Gets the scene for the view.
+  // Returns nullptr if the |TakeScene| was called.
+  mojo::gfx::composition::Scene* scene() { return scene_.get(); }
+
+  // Takes the scene from the view.
+  // This is useful if the scene will be rendered by a separate component.
+  mojo::gfx::composition::ScenePtr TakeScene() { return scene_.Pass(); }
+
+  // |View|:
+  void OnChildUnavailable(uint32_t child_key,
+                          const OnChildUnavailableCallback& callback) override;
+
+ private:
+  mojo::ApplicationImpl* app_impl_;
+
+  mojo::StrongBinding<mojo::ui::View> view_binding_;
+  mojo::ui::ViewManagerPtr view_manager_;
+  mojo::ui::ViewHostPtr view_host_;
+  mojo::ServiceProviderPtr view_service_provider_;
+  mojo::gfx::composition::ScenePtr scene_;
+
+  MOJO_DISALLOW_COPY_AND_ASSIGN(BaseView);
+};
+
+}  // namespace ui
+}  // namespace mojo
+
+#endif  // MOJO_UI_BASE_VIEW_H_