Remove InitializeForUI() from OzonePlatform

ui/ozone/demo/ozone_demo.cc

Index: ui/ozone/demo/ozone_demo.cc
diff --git a/ui/ozone/demo/ozone_demo.cc b/ui/ozone/demo/ozone_demo.cc
index 7b750b34e2bf9ede7780e4d19422d36a2508162d..aa51595d3c421278787a462bf59034eef436dafb 100644
--- a/ui/ozone/demo/ozone_demo.cc
+++ b/ui/ozone/demo/ozone_demo.cc
@@ -339,7 +339,10 @@ int main(int argc, char** argv) {
   base::MessageLoopForUI message_loop;
   base::TaskScheduler::CreateAndSetSimpleTaskScheduler("OzoneDemo");
 
-  ui::OzonePlatform::InitializeForUI();

[tonikitoo, 2017/03/23 11:55:18]

This used to implicitly call "ui::OzonePlatform::InitParams params;" with
default values, where 'single_process' is false.

https://cs.chromium.org/chromium/src/ui/ozone/public/ozone_platform.h?type=cs...

Now, explicitly setting it to 'true' here is a change in the behavior, no?

[Chandan, 2017/03/23 12:13:16]

Generally, we set single_process to true for tests where we expect these to run
in a single process. I assumed the same for ozone demo too. If it's not the
case, I will remove this particular change. Please let me know your opinion.

[fwang, 2017/03/23 13:34:11]

I would personally keep the current behavior, unless there is a reason to do
otherwise. Here MusDemo does not do GL drawing yet so I guess we don't care
about whether the GPU process is separated. Also, most ozone backends ignore
it...

Ideally, I believe single_process should be set according to the
--single-process or --in-process-gpu commands.

[Chandan, 2017/03/27 11:06:40]

Acknowledged.

+  ui::OzonePlatform::InitParams params;
+  params.single_process = true;
+  ui::OzonePlatform::InitializeForUI(params);
+
   ui::KeyboardLayoutEngineManager::GetKeyboardLayoutEngine()
       ->SetCurrentLayoutByName("us");