[MD Extensions] Add a details subpage, move to one list

chrome/browser/resources/md_extensions/manager.html

 <link rel="import" href="chrome://resources/html/cr.html">
 <link rel="import" href="chrome://resources/html/i18n_behavior.html">
 <link rel="import" href="chrome://resources/html/polymer.html">
 <link rel="import" href="chrome://resources/polymer/v1_0/paper-header-panel/paper-header-panel.html">
+<link rel="import" href="chrome://resources/polymer/v1_0/neon-animation/neon-animatable.html">
+<link rel="import" href="chrome://resources/polymer/v1_0/neon-animation/neon-animated-pages.html">
+<link rel="import" href="chrome://extensions/detail_view.html">
 <link rel="import" href="chrome://extensions/item_list.html">
 <link rel="import" href="chrome://extensions/service.html">
 <link rel="import" href="chrome://extensions/sidebar.html">
 <link rel="import" href="chrome://extensions/toolbar.html">
 
 <dom-module id="extensions-manager">
   <template>
     <paper-header-panel id="panel">
       <extensions-toolbar class="paper-header" id="toolbar">
       </extensions-toolbar>
-      <extensions-sidebar in-dev-mode="[[inDevMode]]"
-          hide-extensions-button="[[computeListHidden_(extensions, extensions.splices)]]"

[Devlin, 2016/04/23 01:50:11]

With separate pages for these, I don't think it makes sense to hide the buttons
anymore.  I've asked bettes for confirmation, but this is my hunch.

-          hide-apps-button="[[computeListHidden_(apps, apps.splices)]]"
-          hide-websites-button="[[computeListHidden_(websites, websites.splices)]]">
+      <extensions-sidebar in-dev-mode="[[inDevMode]]">
       </extensions-sidebar>
-      <div id="items">
-        <extensions-item-list id="extensions-list" items="[[extensions]]"
+      <neon-animated-pages id="pages" selected="0">

[Devlin, 2016/04/23 01:50:11]

I talked with michaelpg@ about whether or not to use settings-animated-pages
here, but we figured it was best not to (given that settings-animated-pages is
very heavily linked to settings-router, and, in turn, chrome://settings).  His
recommendation was to go with this.

+        <extensions-item-list id="items-list" items="[[extensions]]"
             delegate="[[service]]" header="[[i18n('sidebarExtensions')]]"
             in-dev-mode="[[inDevMode]]" filter="[[filter]]"
-            hidden$="[[computeListHidden_(extensions, extensions.splices)]]">
+            hidden$="[[computeListHidden_(extensions, extensions.splices, apps, apps.splices)]]">
         </extensions-item-list>
-        <extensions-item-list id="apps-list" items="[[apps]]"
-            delegate="[[service]]" header="[[i18n('sidebarApps')]]"
-            in-dev-mode="[[inDevMode]]" filter="[[filter]]"
-            hidden$="[[computeListHidden_(apps, apps.splices)]]">
-        </extensions-item-list>
-        <extensions-item-list id="websites-list" items="[[websites]]"
-            delegate="[[service]]" header="[[i18n('sidebarWebsites')]]"
-            in-dev-mode="[[inDevMode]]" filter="[[filter]]"
-            hidden$="[[computeListHidden_(websites, websites.splices)]]">
-        </extensions-item-list>
-      </div>
+        <extensions-detail-view id="details-view"
+            on-close="onDetailsViewClose_">
+        </extensions-detail-view>
+      </neon-animated-pages>
     </paper-header-panel>
   </template>
   <link rel="import" type="css" href="chrome://extensions/manager.css">
   <script src="chrome://extensions/manager.js"></script>
 </dom-module>