Policy: generate boilerplate policy type and constant code.

chrome/app/policy/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 485 matching lines @@
           'type': 'list',
           'supported_on': ['chrome.*:8-'],
           'annotations': {
             'features': {'dynamic_refresh': 1},
             'example_value': ['UTF-8', 'UTF-16', 'GB2312', 'ISO-8859-1']
           }
         },
       ]
     },
     {
+      'name': 'BlockThirdPartyCookies',
+      'type': 'main',
+      'supported_on': ['chrome.*:10-'],
+      'annotations': {
+        'features': {'dynamic_refresh': 1},
+        'example_value': False,
+      }

[gfeher, 2011/01/04 12:58:06]

Why are you adding this here?

[danno, 2011/01/11 13:03:48]

This was missing in the JSON file but the constants were used in the code (the
policy is implemented). Now the policy constants are generated, so the policy
actually have to be in the JSON file for things to compile. 

+    },
+    {
       'name': 'ContentSettings',
       'type': 'group',
       'policies': [
         {
           'name': 'DefaultCookiesSetting',
           'type': 'enum',
           'items': [
             {'name': 'AllowCookies', 'value': '0'},
             {'name': 'BlockCookies', 'value': '1'},
           ],
@@ skipping 161 matching lines @@
     {
       'key': '$4',
       'value': 'http://www.chromium.org/developers/how-tos/chrome-frame-getting-started'
     },
     {
       'key': '$5',
       'value': 'http://www.chromium.org/administrators/policy-templates'
     },
   ]
 }