Implement the new wallpaper manager launcher window.

chrome/browser/resources/chromeos/wallpaper_manager/js/main.js

Index: chrome/browser/resources/chromeos/wallpaper_manager/js/main.js
diff --git a/chrome/browser/resources/chromeos/wallpaper_manager/js/main.js b/chrome/browser/resources/chromeos/wallpaper_manager/js/main.js
new file mode 100644
index 0000000000000000000000000000000000000000..facfd667e38cb3f35d12a71e61a4bf5bde8d3360
--- /dev/null
+++ b/chrome/browser/resources/chromeos/wallpaper_manager/js/main.js
@@ -0,0 +1,13 @@
+// Copyright (c) 2012 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.
+
+function init() {
+  var windowStateManager =
+      chrome.extension.getBackgroundPage().windowStateManager;

[Vladislav Kaznacheev, 2012/07/06 10:57:13]

Why do you need to keep the state in the background page? Do you expect to have
more than one wallpaper manager window open?

[bshe, 2012/07/06 18:58:06]

When wallpaper manager window opens, it hides all existing browser windows are
minimized so user can see their choice of wallpaper more clearly. But after
window manager closed, we want to restore the state of all existing windows. So
I keep the state in the background page. I would not expect to have more than
one wallpaper manager open but I haven't implement the check yet.

On 2012/07/06 10:57:13, Vladislav Kaznacheev wrote:

+  windowStateManager.saveStates();
+  window.addEventListener('unload',
+      windowStateManager.restoreStates.bind(windowStateManager));
+}
+
+document.addEventListener('DOMContentLoaded', init);