Refactor app list ContentsView to use pointer members to find views.

ui/app_list/views/contents_view.h

Index: ui/app_list/views/contents_view.h
diff --git a/ui/app_list/views/contents_view.h b/ui/app_list/views/contents_view.h
index 670eae169a4a7f05d4461e6712c33f8527aa6d57..e7df7bc0ccbf4b75207aaa04856e5a12c7561ebb 100644
--- a/ui/app_list/views/contents_view.h
+++ b/ui/app_list/views/contents_view.h
@@ -30,6 +30,7 @@ class AppListModel;
 class AppListViewDelegate;
 class AppsContainerView;
 class PaginationModel;
+class SearchResultListView;
 class StartPageView;
 
 // A view to manage sub views under the search box (apps grid view + page
@@ -92,8 +93,10 @@ class APP_LIST_EXPORT ContentsView : public views::View {
 
   ShowState show_state_;
 
-  AppsContainerView* apps_container_view_;  // Owned by the views hierarchy.
-  StartPageView* start_page_view_;          // Owned by the views hierarchy.
+  // Special sub views of the ContentsView. All owned by the views hierarchy.

[benwells, 2014/06/05 06:33:45]

How are they special??

[Matt Giuca, 2014/06/05 06:54:11]

"Special" means that we need hard-coded access to them from our code. At the
moment, they're all special (just like snowflakes). But once we start adding
dynamic pages, this will make more sense because they won't be considered
special.

+  AppsContainerView* apps_container_view_;
+  SearchResultListView* search_results_view_;
+  StartPageView* start_page_view_;
 
   AppListMainView* app_list_main_view_;     // Parent view, owns this.