Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(6795)

Unified Diff: chrome/common/extensions/docs/server2/templates/articles/experimental.html

Issue 10815042: Extensions Docs Server: api_index.html, experimental.html (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 8 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: chrome/common/extensions/docs/server2/templates/articles/experimental.html
diff --git a/chrome/common/extensions/docs/server2/templates/articles/experimental.html b/chrome/common/extensions/docs/server2/templates/articles/experimental.html
new file mode 100644
index 0000000000000000000000000000000000000000..a1f152cb3de5bae79cf11c1b03c7e065be71f397
--- /dev/null
+++ b/chrome/common/extensions/docs/server2/templates/articles/experimental.html
@@ -0,0 +1,124 @@
+<h1>chrome.experimental.* APIs</h1>
+<div class="doc-family extensions">
+<p>
+Before you start, <strong>choose the right version of this page.</strong>
+You should read either:
+</p>
+
+<ul>
+ <li> <a href="http://code.google.com/chrome/extensions/trunk/experimental.html">Most recent experimental APIs</a>
+ <li> <a href="http://code.google.com/chrome/extensions/dev/experimental.html">Dev channel experimental APIs</a></li>
+</ul>
+
+<p>
+For information about browser versions such as
+Canary (bleeding edge) and the Dev channel, see
+<a href="http://www.chromium.org/getting-involved/dev-channel">Chrome Release Channels</a>.
+For details about channel-specific docs,
+see <a href="docs.html#versions">Doc versions</a>.
+</p>
+</div>
+
+<h2 id="overview">
+List of APIs
+</h2>
+
+<p class="doc-family extensions">
+We'd like your <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/topics">feedback</a>
+on the following experimental APIs:
+</p>
+
+<ul>
+ {{#api_list.list.experimental}}
+ <li><a href="{{@}}.html">{{@}}</a></li>
+ {{/}}
+</ul>
+
+<p class="doc-family extensions">
+Pay special attention to the following APIs,
+which we expect to finalize soon:
+<b>devtools</b>,
+<b>infobars</b>,
+<b>permissions</b>,
+For examples of using the experimental APIs, see
+<a href="samples.html#experimental">Samples</a>.
+</p>
+
+<p class="warning">
+<b>Caution:</b>
+Don't depend on these experimental APIs.
+They might disappear,
+and they <em>will</em> change.
+Also, the Chrome Web Store doesn't allow you to
+upload items that use experimental APIs.
+</p>
+
+
+<h2 id="using">How to use experimental APIs</h2>
+
+<ol>
+ <li class="doc-family extensions">
+ Make sure you're using either
+ <a href="http://tools.google.com/dlpage/chromesxs">Canary</a>
+ (which you can use at the same time as other Chrome channels) or the
+<a href="http://www.chromium.org/getting-involved/dev-channel">Dev channel</a>.
+ Although the experimental APIs might work in other versions,
+ we need your feedback on the latest incarnation of the APIs,
+ which you can find in Canary and on the Dev channel.
+ </li>
+ <li class="doc-family extensions">
+ Using either the
+ <a href="http://code.google.com/chrome/extensions/trunk/experimental.html">most recent API documentation</a> (if you're using Canary) or the
+ <a href="http://code.google.com/chrome/extensions/dev/experimental.html">API documentation for the Dev channel</a>,
+ write the code for your extension.
+ </li>
+ <li>
+ Specify the "experimental"
+ <a href="manifest.html#permissions">permission</a>
+ in your manifest, like this:
+<pre>
+"permissions": [
+ <b>"experimental"</b>,
+ ...
+],
+</pre>
+ </li>
+ <li>
+ Enable the experimental API in your browser.
+ You can do this in either of two ways:
+ <ul>
+ <li> Go to <b>chrome://flags</b>,
+ find "Experimental Extension APIs",
+ click its "Enable" link,
+ and restart Chrome.
+ From now on,
+ unless you return to that page and disable experimental APIs,
+ you'll be able to run extensions and apps that use experimental APIs.
+ </li>
+ <li> Specify the <b>--enable-experimental-extension-apis</b> flag
+ each time you launch the browser.
+ On Windows, you can do this by modifying
+ the properties of the shortcut that you use to launch Google Chrome.
+ For example:
+
+<pre>
+<em>path_to_chrome.exe</em> <b>--enable-experimental-extension-apis</b></pre>
+ </li>
+ </ul>
+ </li>
+
+ <li class="doc-family extension">
+ <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/topics">Give us feedback!</a>
+ Your comments and suggestions help us
+ improve the APIs and decide
+ which ones should move from experimental to supported.
+ </li>
+</ol>
+
+<h2 id="other">More APIs</h2>
+
+<p>
+For information on the standard APIs that packaged apps can use, see
+<a href="api_index.html">chrome.* APIs</a> and
+<a href="api_other.html">Other APIs</a>.
+</p>

Powered by Google App Engine
This is Rietveld 408576698