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..6c0c574513c07840e705ad1db6ba0086a55bdeab 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,24 @@
       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': True,
+        'per_profile': True
+      },
+      'example_value': False,
+      'id': 268,
+      'caption': '''Enable virtual keyboard''',
+      'desc': '''This policy configures enabling the virtual keyboard as an input device on ChromeOS. Users cannot override this policy.
+
+      If the policy is set to true, the virtual keyboard will be enabled and cannot be disabled. If set to false, the virtual keyboard will be disabled by default, however may appear if the user explicitly enables the accessibility keyboard.

[bartfab (slow), 2014/06/16 10:20:13]

Nit: Maybe it would make sense to differentiate between the regular VK and a11y
VK here? E.g. something along the lines of:

If the policy is set to true, the on-screen virtual keyboard will always be
enabled.

If this policy is set to false, the on-screen keyboard will always be disabled.

If you set this policy, users cannot change or override it. However, users will
still be able to enable/disable an accessibility on-screen keyboard which takes
precedence over the virtual keyboard controlled by this policy. See the
|VirtualKeyboardEnabled| policy for controlling the accessibility on-screen
keyboard.

[rsadam, 2014/06/16 13:45:34]

Done.

+
+      If unset, this policy will have no effect - the virtual keyboard is disabled by default, but may appear if a user enables it. Heuristic rules may also be used to decide when to display the keyboard.''',

[bartfab (slow), 2014/06/16 10:20:13]

Very minor nit: You could make this slightly more consistent with other
policies, and especially the a11y keyboard policy, by rewording it to:

If this policy is left unset, the on-screen keyboard is disabled initially but
can be enabled by the user anytime. Heuristic rules may also be used to decide
when to display the keyboard.

[rsadam, 2014/06/16 13:45:34]

Done.

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