Scaffold for MD-Settings, inside chrome://md-settings.

chrome/browser/resources/settings/settings.js

Index: chrome/browser/resources/settings/settings.js
diff --git a/chrome/browser/resources/settings/settings.js b/chrome/browser/resources/settings/settings.js
new file mode 100644
index 0000000000000000000000000000000000000000..be55ecf4e12f83e52fc4fed3e968783ec639af2c
--- /dev/null
+++ b/chrome/browser/resources/settings/settings.js
@@ -0,0 +1,37 @@
+// 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.
+
+/**
+ * @fileoverview
+ * 'cr-settings' is the main MD-Settings element, combining the UI and models
+ * and controlling which pages are shown.
+ *
+ * Example:
+ *
+ *    <cr-settings></cr-settings>
+ *
+ * @group Chrome Settings Elements
+ * @element cr-settings
+ */
+Polymer('cr-settings', {
+  /**
+   * Settings pages available to the user.
+   *
+   * @private Array<!CrSettingsPage>
+   */
+  pages_: [],
+
+  /** @override */
+  ready: function() {
+    // Add pages depending on the platform. Pages should be imported in
+    // settings.html.
+    if (utils.isChromeOs())
+      this.pages_.push(new CrSettingsA11yPage());

[Jeremy Klein, 2015/03/07 23:55:13]

I really still feel like I'd rather do this declaratively. I like being able to
see the dom structure in the HTML with the pages. That would also allow you to
tie up the prefs in the html.

+
+    this.pages_.push(new CrSettingsDummyPage());
+
+    for (var i = 0; i < this.pages_.length; i++)
+      this.pages_[i].prefs = this.$.settings;
+  },
+});