Move UI specific implementation from ProfileSyncService to SyncSetupFlowHandler.

chrome/browser/sync/sync_setup_wizard.cc

Index: chrome/browser/sync/sync_setup_wizard.cc
diff --git a/chrome/browser/sync/sync_setup_wizard.cc b/chrome/browser/sync/sync_setup_wizard.cc
index b8dc3dd27d94d098911a45d81cdf6818a39a8a12..18315e1bd0b154d57f7482152c2e2d8c5369c072 100644
--- a/chrome/browser/sync/sync_setup_wizard.cc
+++ b/chrome/browser/sync/sync_setup_wizard.cc
@@ -83,6 +83,18 @@ void SyncSetupWizard::Focus() {
     flow->Focus();
 }
 
+void SyncSetupWizard::ShowSyncSetup(State state) {
+  SyncSetupFlow* flow = flow_container_->get_flow();
+  if (flow) {
+    flow->Focus();
+    return;

[Andrew T Wilson (Slow), 2011/07/11 18:12:51]

Don't we still need to Step in the case that there's already a flow object?

[qsr (NOT THE RIGHT qsr), 2011/07/12 07:01:37]

If you look at what was done in ProfileSyncService, there was not step done if
the wizard was visible. Mainly, the ShowSyncSetup must only be called to start a
new flow, otherwise it will just focus the UI.

+  }
+  Step(state);
+  flow = flow_container_->get_flow();
+  if (flow)
+    flow->ShowSyncSetup();

[tim (not reviewing), 2011/07/11 14:44:25]

I think I see what changed that caused my confusion last week... Flow::Run did
indeed used to "show" the UI, but it was removed ~6 weeks ago by
http://codereview.chromium.org/7057038.  But the method is still named Run,
which is really confusing to me.  

Could we not have Run(...) call flow_handler-> ShowSyncSetup, akin to how it
worked before that CR above, and then not need this new method?

+}
+
 SyncSetupFlow* SyncSetupWizard::AttachSyncSetupHandler(
     SyncSetupFlowHandler* handler) {
   SyncSetupFlow* flow = flow_container_->get_flow();