Scaffold for MD-Settings.

chrome/browser/resources/settings/settings_ui/settings_ui.js

Index: chrome/browser/resources/settings/settings_ui/settings_ui.js
diff --git a/chrome/browser/resources/settings/settings_ui/settings_ui.js b/chrome/browser/resources/settings/settings_ui/settings_ui.js
new file mode 100644
index 0000000000000000000000000000000000000000..9051f6ffece184df3b32f5fe1764622f385c51d9
--- /dev/null
+++ b/chrome/browser/resources/settings/settings_ui/settings_ui.js
@@ -0,0 +1,45 @@
+// 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-ui' implements the UI for the Settings page.
+ *
+ * Example:
+ *
+ *    <cr-settings-ui prefs="{{prefs}}"></cr-settings-ui>
+ *
+ * @group Chrome Settings Elements
+ * @element cr-settings-ui
+ */
+Polymer('cr-settings-ui', {
+  publish: {
+    /**
+     * Preferences state.
+     *
+     * @attribute prefs
+     * @type CrSettingsPrefsElement
+     * @default null
+     */
+    prefs: null,
+
+    /**
+     * Ordered list of settings pages available to the user.
+     *
+     * To avoid unnecessary DOM manipulation, prefer using Array.prototype

[Jeremy Klein, 2015/03/12 02:11:18]

Is this comment still applicable if we add the pages declaratively? Maybe even
just saying "Don't edit this variable directly" is enough.

[michaelpg, 2015/03/12 06:29:37]

Done.

+     * functions on this attribute rather than replacing it with a new array
+     * after setting the attribute initially.
+     *
+     * @attribute pages
+     * @type Array<!Object>
+     * @default null
+     */
+    pages: null,
+  },
+
+  /** @override */
+  created: function() {
+    this.pages = [];
+  },
+});