Add an experimental permissions API for extensions.

chrome/browser/extensions/extension_permissions_api_constants.cc

Index: chrome/browser/extensions/extension_permissions_api_constants.cc
diff --git a/chrome/browser/extensions/extension_permissions_api_constants.cc b/chrome/browser/extensions/extension_permissions_api_constants.cc
new file mode 100644
index 0000000000000000000000000000000000000000..c22686c84f837359a62ddaf2e63794fa7ffe4e97
--- /dev/null
+++ b/chrome/browser/extensions/extension_permissions_api_constants.cc
@@ -0,0 +1,23 @@
+// Copyright (c) 2011 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "chrome/browser/extensions/extension_permissions_api_constants.h"
+
+namespace extension_permissions_module_constants {
+
+const char kApisKey[] = "apis";

[Mihai Parparita -not on Chrome, 2011/07/20 22:03:43]

Not sure "apis" is the best name, since it's not always a 1:1 mapping between
APIs and permissions (e.g. chrome.tabs and chrome.windows are both controlled by
the "tabs" permission). Do you think it'd be too confusing to just call it
"permissions"? (even if you later add "origins" as a separate field?)

[jstritar, 2011/07/22 19:21:55]

Changed this to "permissions". I'll update the terminology in
ExtensionPermissionSet in a follow up CL.

+
+const char kCantRemoveRequiredPermissionsError[] =
+    "You cannot remove required permissions.";
+const char kNotInOptionalPermissionsError[] =
+    "Optional permissions must be listed in extension manifest.";
+const char kNotWhiteListedError[] =
+    "The optional permissions API does not support '%s'.";
+const char kUnknownPermissionError[] =
+    "'%s' is not a recognized permission.";
+
+const char kOnAdded[] = "permissions.onAdded";
+const char kOnRemoved[] = "permissions.onRemoved";
+
+};  // namespace extension_permissions_module_constants