chrome/common/extensions/docs/server2/templates/articles/experimental.html - Issue 10834144: Extensions Docs Server: Split apps from extensions

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

Issue 10834144: Extensions Docs Server: Split apps from extensions (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: reworked Created 8 years, 4 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 unified diff | Download patch | Annotate | Revision Log

« chrome/common/extensions/docs/server2/templates/articles/api_index_extensions.html ('K') | « chrome/common/extensions/docs/server2/templates/articles/api_index_extensions.html ('k') | chrome/common/extensions/docs/server2/templates/articles/experimental_apps.html » ('j') | chrome/common/extensions/docs/server2/templates/articles/experimental_extensions.html » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
	(Empty)
1 <h1 class="page_title">chrome.experimental.* APIs</h1>

2 <div class="doc-family extensions">

3 <p>

4 Before you start, <strong>choose the right version of this page.</strong>

5 You should read either:

6 </p>

7

8 <ul>

9 <li> <a href="http://code.google.com/chrome/extensions/trunk/experimental.html ">Most recent experimental APIs</a>

10 <li> <a href="http://code.google.com/chrome/extensions/dev/experimental.html"> Dev channel experimental APIs</a></li>

11 </ul>

12

13 <p>

14 For information about browser versions such as

15 Canary (bleeding edge) and the Dev channel, see

16 <a href="http://www.chromium.org/getting-involved/dev-channel">Chrome Release Ch annels</a>.

17 For details about channel-specific docs,

18 see <a href="docs.html#versions">Doc versions</a>.

19 </p>

20 </div>

21

22 <h2 id="overview">

23 List of APIs

24 </h2>

25

26 <p class="doc-family extensions">

27 We'd like your <a href="http://groups.google.com/a/chromium.org/group/chromium-e xtensions/topics">feedback</a>

28 on the following experimental APIs:

29 </p>

30

31 <ul>

32 {{#api_list.experimental}}

33 <li><a href="{{name}}.html">{{name}}</a></li>

34 {{/}}

35 </ul>

36

37 <p class="doc-family extensions">

38 Pay special attention to the following APIs,

39 which we expect to finalize soon:

40 <b>devtools</b>,

41 <b>infobars</b>,

42 <b>permissions</b>,

43 For examples of using the experimental APIs, see

44 <a href="samples.html#experimental">Samples</a>.

45 </p>

46

47 <p class="warning">

48 <b>Caution:</b>

49 Don't depend on these experimental APIs.

50 They might disappear,

51 and they <em>will</em> change.

52 Also, the Chrome Web Store doesn't allow you to

53 upload items that use experimental APIs.

54 </p>

55

56

57 <h2 id="using">How to use experimental APIs</h2>

58

59 <ol>

60 <li class="doc-family extensions">

61 Make sure you're using either

62 <a href="http://tools.google.com/dlpage/chromesxs">Canary</a>

63 (which you can use at the same time as other Chrome channels) or the

64 <a href="http://www.chromium.org/getting-involved/dev-channel">Dev channel</a>.

65 Although the experimental APIs might work in other versions,

66 we need your feedback on the latest incarnation of the APIs,

67 which you can find in Canary and on the Dev channel.

68 </li>

69 <li class="doc-family extensions">

70 Using either the

71 <a href="http://code.google.com/chrome/extensions/trunk/experimental.html">m ost recent API documentation</a> (if you're using Canary) or the

72 <a href="http://code.google.com/chrome/extensions/dev/experimental.html">API documentation for the Dev channel</a>,

73 write the code for your extension.

74 </li>

75 <li>

76 Specify the "experimental"

77 <a href="manifest.html#permissions">permission</a>

78 in your manifest, like this:

79 <pre>

80 "permissions": [

81 <b>"experimental"</b>,

82 ...

83 ],

84 </pre>

85 </li>

86 <li>

87 Enable the experimental API in your browser.

88 You can do this in either of two ways:

89 <ul>

90 <li> Go to <b>chrome://flags</b>,

91 find "Experimental Extension APIs",

92 click its "Enable" link,

93 and restart Chrome.

94 From now on,

95 unless you return to that page and disable experimental APIs,

96 you'll be able to run extensions and apps that use experimental APIs.

97 </li>

98 <li> Specify the <b>--enable-experimental-extension-apis</b> flag

99 each time you launch the browser.

100 On Windows, you can do this by modifying

101 the properties of the shortcut that you use to launch Google Chrome.

102 For example:

103

104 <pre>

105 <em>path_to_chrome.exe</em> <b>--enable-experimental-extension-apis</b></pre>

106 </li>

107 </ul>

108 </li>

109

110 <li class="doc-family extension">

111 <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/t opics">Give us feedback!</a>

112 Your comments and suggestions help us

113 improve the APIs and decide

114 which ones should move from experimental to supported.

115 </li>

116 </ol>

117

118 <h2 id="other">More APIs</h2>

119

120 <p>

121 For information on the standard APIs that packaged apps can use, see

122 <a href="api_index.html">chrome.* APIs</a> and

123 <a href="api_other.html">Other APIs</a>.

124 </p>

OLD	NEW