Add device policy: Kiosk Virtual Keyboard Layout.

components/policy/resources/policy_templates.json

Index: components/policy/resources/policy_templates.json
diff --git a/components/policy/resources/policy_templates.json b/components/policy/resources/policy_templates.json
index c9a140590216c9ff1537460c6ebcc9397b9743d7..24052040babfb70933401dca384623ba4b173cfa 100644
--- a/components/policy/resources/policy_templates.json
+++ b/components/policy/resources/policy_templates.json
@@ -118,7 +118,7 @@
 #   persistent IDs for all fields (but not for groups!) are needed. These are
 #   specified by the 'id' keys of each policy. NEVER CHANGE EXISTING IDs,
 #   because doing so would break the deployed wire format!
-#   For your editing convenience: highest ID currently used: 267
+#   For your editing convenience: highest ID currently used: 268
 #
 # Placeholders:
 #   The following placeholder strings are automatically substituted:
@@ -4660,6 +4660,20 @@
       If this policy is not set, the device will default to a 24 hour clock format.''',
     },
     {
+      'name': 'TouchVirtualKeyboardEnabled',
+      'type': 'main',
+      'schema': { 'type': 'boolean' },
+      'supported_on': ['chrome_os:37-' ],
+      'features': {
+        'dynamic_refresh': False,

[bartfab (slow), 2014/06/13 12:15:53]

Can you make the code honor pref changes on the fly? It is good to support
dynamic_refresh when there are no technical obstacles.

[rsadam, 2014/06/13 15:28:47]

Done.

+        'per_profile': True
+      },
+      'example_value': False,
+      'id': 268,
+      'caption': '''Enable Virtual Keyboard''',

[bartfab (slow), 2014/06/13 12:15:53]

Nit: s/Virtual Keyboard/virtual keyboard/

[rsadam, 2014/06/13 15:28:47]

Done.

+      'desc': '''If unset this policy has no effect. If true, this enables the virtual keyboard. If false, this disables the virtual keyboard. If the accessibility virtual keyboard policy is set to true, it takes precedence over this.''',

[bartfab (slow), 2014/06/13 12:15:53]

Take a look at the other policy descriptions. They are not 100% consistent but
they do follow a rough pattern: There should be several paragraph. The first
paragraph repeats what the policy is about, in a more verbose way than the
pattern. The next paragraphs describe what the different policy values do. They
should also state that when the policy is set, the user cannot override it. It
is definitely a good idea to mention at that point how the policy interacts with
the a11y keyboard. And finally, a last paragraph describes the default behavior
when the policy is unset.

[rsadam, 2014/06/13 15:28:47]

Done.

+    },
+    {
       'name': 'ShowLogoutButtonInTray',
       'type': 'main',
       'schema': { 'type': 'boolean' },