Implementing --app-launcher install/uninstall flow.

chrome/installer/setup/install.cc

Index: chrome/installer/setup/install.cc
diff --git a/chrome/installer/setup/install.cc b/chrome/installer/setup/install.cc
index 2f4029c64e99a52944df42e07fec087eb199eb6c..89de9adea1716fb20993866cdc6f3b0340b4a167 100644
--- a/chrome/installer/setup/install.cc
+++ b/chrome/installer/setup/install.cc
@@ -350,23 +350,23 @@ void CreateOrUpdateShortcuts(const InstallerState& installer_state,
   DCHECK(product.is_chrome());
 
   BrowserDistribution* dist = product.distribution();
-  const FilePath chrome_exe(
-      installer_state.target_path().Append(installer::kChromeExe));
   ShellUtil::ShellChange install_level =
       installer_state.system_install() ? ShellUtil::SYSTEM_LEVEL :
                                          ShellUtil::CURRENT_USER;
+  // |base_properties|: The basic properties to set on every shortcut installed

[grt (UTC plus 2), 2012/10/30 13:02:55]

please revert all shortcut-related changes if you're not doing them in this CL.

[erikwright (departed), 2012/10/30 14:20:39]

Feel free to ask for help to split them into a separate CL without losing them.

[huangs, 2012/10/30 20:35:07]

Will remove the "if".  The rest is just minor cleanup.  Will remove if you
insist.

[gab, 2012/10/30 21:30:40]

I don't see how the changes in install.cc/uninstall.cc are at all
necessary/useful by themselves.

I'm sure other things motivated the changes, but the motivation should come
along with the change, no point doing this in this CL imo.

[huangs, 2012/10/30 21:38:39]

I didn't want these trivial changes to add visual clutter when the real stuff
comes.  But oh well; removing them.

[erikwright (departed), 2012/10/30 22:53:52]

If the changes are good refactorings that stand on their own, create a separate
CL for them alone. Don't bundle stuff into other CLs just because it's
convenient (it's not convenient for your reviewers).

It's also not convenient for you. For example, if something causes you to revert
this CL, you will now be reverting more code. And what if someone then starts
coding against your refactored API? Now your revert gets harder.

And you are more likely to have to revert the more code you change. Or more
likely to fail to commit due to a merge conflict, etc.

+  // (to be refined on a per-shortcut basis).
+  ShellUtil::ChromeShortcutProperties base_properties(install_level);
+
+  if (product.is_chrome()) {
+    base_properties.set_chrome_exe(
+        installer_state.target_path().Append(installer::kChromeExe));
+  }
 
   // The default operation on update is to overwrite shortcuts with the
   // currently desired properties, but do so only for shortcuts that still
   // exist.
   ShellUtil::ChromeShortcutOperation shortcut_operation =
       ShellUtil::SHORTCUT_REPLACE_EXISTING;
-
-  // |base_properties|: The basic properties to set on every shortcut installed
-  // (to be refined on a per-shortcut basis).
-  ShellUtil::ChromeShortcutProperties base_properties(install_level);
-  base_properties.set_chrome_exe(chrome_exe);
-
   // If |install_operation| is INSTALL_SHORTCUT_CREATE_ALL, create optional
   // shortcuts (Desktop and Quick Launch) immediately; otherwise delay their
   // creation until first run.
@@ -401,7 +401,7 @@ void CreateOrUpdateShortcuts(const InstallerState& installer_state,
 
   ShellUtil::ChromeShortcutProperties start_menu_properties(base_properties);
   // IMPORTANT: Only the default (no arguments and default browserappid) browser
-  // shortcut in the Start menu (Start screen on Win8+) should be  made dual
+  // shortcut in the Start menu (Start screen on Win8+) should be made dual
   // mode.
   start_menu_properties.set_dual_mode(true);
   if (shortcut_operation == ShellUtil::SHORTCUT_CREATE_ALWAYS)