Experimental app list: Added a current page indicator to the launcher.

ui/app_list/views/contents_switcher_view.h

Index: ui/app_list/views/contents_switcher_view.h
diff --git a/ui/app_list/views/contents_switcher_view.h b/ui/app_list/views/contents_switcher_view.h
index 3f1bbf40ea17bdbbf39d4335ba5565ba9e51ab47..09059bf51c6d55c22d8650aa7eb63f52a74db652 100644
--- a/ui/app_list/views/contents_switcher_view.h
+++ b/ui/app_list/views/contents_switcher_view.h
@@ -27,6 +27,9 @@ class ContentsSwitcherView : public views::View, public views::ButtonListener {
   // is ignored if it is 0.
   void AddSwitcherButton(int resource_id, int page_index);
 
+  // Changes the launcher page indicator to the selected page.
+  void SelectedPageChanged(int old_selected, int new_selected);
+
  private:
   // Overridden from views::View:
   virtual gfx::Size GetPreferredSize() const OVERRIDE;
@@ -38,6 +41,8 @@ class ContentsSwitcherView : public views::View, public views::ButtonListener {
 
   ContentsView* contents_view_;  // Owned by views hierarchy.
   views::View* buttons_;         // Owned by views hierarchy.
+  // Stores Views owned by views hierarchy.
+  std::vector<views::View*> page_active_indicators_;

[Matt Giuca, 2014/07/09 07:01:20]

I'm not sure if this is the right approach. We eventually want to have an
animation showing a single blue indicator sliding between the buttons, which
means ultimately we're going to want a single ContentsPageIndicatorView which
moves (rather than an array of hidden ones, and one visible one).

If it's possible to do this now, I think you should. It's debatable whether you
should submit this now, and then change it over to the other approach, or
whether it isn't worth submitting this change unless that is done (because the
final approach will be very different). You can decide or we can discuss.

[calamity, 2014/07/09 08:02:54]

From a short discussion w/ Matt: We don't know what we want. We can defer this
decision for now.

 
   DISALLOW_COPY_AND_ASSIGN(ContentsSwitcherView);
 };