Add device policy: Kiosk Virtual Keyboard Layout.

components/policy/resources/policy_templates.json

 {
 # policy_templates.json - Metafile for policy templates
 #
 # The content of this file is evaluated as a Python expression.
 #
 # This file is used as input to generate the following policy templates:
 # ADM, ADMX+ADML, MCX/plist and html documentation.
 #
 # Policy templates are user interface definitions or documents about the
 # policies that can be used to configure Chrome. Each policy is a name-value
@@ skipping 100 matching lines @@
 #   templates and documentation. The policy definition list that Chrome sees
 #   will include policies marked with 'future'. If a WIP policy isn't meant to
 #   be seen by the policy providers either, the 'supported_on' key should be set
 #   to an empty list.
 #
 # IDs:
 #   Since a Protocol Buffer definition is generated from this file, unique and
 #   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:
 #     $1 -> Google Chrome / Chromium
 #     $2 -> Google Chrome OS / Chromium OS
 #     $3 -> Google Chrome Frame / Chromium Frame
 #     $6 is reserved for doc_writer
 #
 # Device Policy:
 #   An additional flag device_only (optional, defaults to False) indicates
@@ skipping 4521 matching lines @@
       'caption': '''Use 24 hour clock by default''',
       'desc': '''Specifies the clock format be used for the device.
 
       This policy configures the clock format to use on the login screen and as a default for user sessions. Users can still override the clock format for their account.
 
       If the policy is not set to true, the device will use a 24 hour clock format. If the policy is set to false, the device will use 12 hour clock format.
 
       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' },
       'supported_on': ['chrome_os:25-'],
       'features': {
         'dynamic_refresh': True,
         'per_profile': True,
       },
       'example_value': True,
       'id': 164,
@@ skipping 1862 matching lines @@
       'desc': '''Text appended in parentheses to the policy name to indicate that it has been deprecated''',
       'text': 'deprecated',
     },
     'doc_recommended': {
       'desc': '''Text appended in parentheses next to the policies top-level container to indicate that those policies are of the Recommended level''',
       'text': 'Default Settings (users can override)',
     },
   },
   'placeholders': [],
 }