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': 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' },
       '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': [],
 }