[Ozone-Demo] Initialize a default keyboard layout

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 bbb63076d1c1622639cb4b16902a6b1fc6d1261d..32d7fde700b5e46cc1fd03965ce0f80f0cd0e837 100644
--- a/ui/ozone/demo/ozone_demo.cc
+++ b/ui/ozone/demo/ozone_demo.cc
@@ -9,6 +9,8 @@
 #include "base/timer/timer.h"
 #include "ui/events/event.h"
 #include "ui/events/keycodes/dom3/dom_code.h"
+#include "ui/events/ozone/layout/keyboard_layout_engine.h"
+#include "ui/events/ozone/layout/keyboard_layout_engine_manager.h"
 #include "ui/gfx/geometry/rect.h"
 #include "ui/gfx/geometry/size.h"
 #include "ui/gl/gl_surface.h"
@@ -136,6 +138,8 @@ int main(int argc, char** argv) {
   base::MessageLoopForUI message_loop;
 
   ui::OzonePlatform::InitializeForUI();
+  ui::KeyboardLayoutEngineManager::GetKeyboardLayoutEngine()
+      ->SetCurrentLayoutByName("us");

[alexst (slow to review), 2015/01/13 21:41:31]

Is "us" a know string or is it just something that would fall back to default
because there is nothing available. Is there maybe a better way to say this is
the default one?

[dnicoara, 2015/01/13 21:46:04]

"us" is a known layout. The issue is there is no default layout installed when
running the demo so all key events are just ignored. On ChromeOS builds, CrOS
will set a layout, so this wouldn't be an issue. Kevin is looking at having a
default/fallback layout, but in the meantime I thought it may be useful to have
something.

 
   base::RunLoop run_loop;