First try at a user management screen for the desktop

chrome/browser/profiles/profile_manager.cc

Index: chrome/browser/profiles/profile_manager.cc
diff --git a/chrome/browser/profiles/profile_manager.cc b/chrome/browser/profiles/profile_manager.cc
index 7be5e410698770f015262982dd9329ff8a1fd1fb..9398d6cc0abcd62f544c52fbc30f7307ab6603ed 100644
--- a/chrome/browser/profiles/profile_manager.cc
+++ b/chrome/browser/profiles/profile_manager.cc
@@ -166,6 +166,22 @@ bool IsProfileMarkedForDeletion(const base::FilePath& profile_path) {
       profile_path) != ProfilesToDelete().end();
 }
 
+void OpenBrowserWindowForProfile(bool always_create,
+                                 chrome::HostDesktopType desktop_type,
+                                 Profile* profile,
+                                 Profile::CreateStatus status) {
+  DCHECK(BrowserThread::CurrentlyOn(BrowserThread::UI));
+
+  if (status == Profile::CREATE_STATUS_INITIALIZED) {
+    ProfileManager::FindOrCreateNewWindowForProfile(
+        profile,
+        chrome::startup::IS_NOT_PROCESS_STARTUP,
+        chrome::startup::IS_NOT_FIRST_RUN,
+        desktop_type,
+        always_create);
+  }
+}
+
 #if defined(OS_CHROMEOS)
 void CheckCryptohomeIsMounted(chromeos::DBusMethodCallStatus call_status,
                               bool is_mounted) {
@@ -628,6 +644,21 @@ void ProfileManager::FindOrCreateNewWindowForProfile(
 #endif  // defined(OS_IOS)
 }
 
+// static
+void ProfileManager::SwitchToProfile(

[sail, 2013/07/02 21:46:40]

I don't think there's any value in having this in ProfileManager. Can we keep
all this in AvatarMenuModel instead?

[noms, 2013/07/03 17:11:35]

The reason I moved it here is that the user chooser page also needs to open a
window for a selected profile, and as it is, it would need to instantiate a
mostly-unused AvatarMenuModel. Roger had suggested in a previous comment to
factor it out to a standalone function. Given that it calls CreateProfileAsync
on the profile manager (and doesn't really do anything about the avatars), I
thought the ProfileManager would be a better place for it. Do you think it
should be a static function in the AvatarMenuModel instead? 

On 2013/07/02 21:46:40, sail wrote:

[sail, 2013/07/03 18:18:04]

Adding this to profile manager is a bad idea.
The profile manager API is already more complicated than it needs to be.

[noms, 2013/07/05 17:39:27]

As discussed offline, this is ok because it's only adding one static function,
that needs to be called from placed that aren't just the AvatarMenuModel, and
whose functionality is only related to the ProfileManager.

On 2013/07/03 18:18:04, sail wrote:

+    const base::FilePath& path,
+    chrome::HostDesktopType desktop_type,
+    bool always_create) {
+  g_browser_process->profile_manager()->CreateProfileAsync(
+      path,
+      base::Bind(&OpenBrowserWindowForProfile,
+                 always_create,
+                 desktop_type),
+      string16(),
+      string16(),
+      false);
+}
+
 void ProfileManager::Observe(
     int type,
     const content::NotificationSource& source,