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

Side by Side Diff: chrome/common/extensions/docs/server2/templates/private/devtools_intro.html

Issue 10750017: Extensions Docs Server: Intro data source (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: nits 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 unified diff | Download patch | Annotate | Revision Log
OLDNEW
(Empty)
1 <p>
2 The following API modules provide support for extending
3 Chrome Developer Tools:
4 </p>
5
6 <a name="api-list"></a>
7 <ul>
8 <li>
9 <a href="devtools.inspectedWindow.html">devtools.inspectedWindow</a></li><li>
10 <a href="devtools.network.html">devtools.network</a></li><li>
11 <a href="devtools.panels.html">devtools.panels</a></li>
12 </ul>
13
14 <h2 id="using">How to use DevTools APIs</h2>
15
16 <ol>
17 <li>
18 Specify the "devtools_page" field in your extension's manifest:
19 <pre>{
20 "name": ...
21 "version": "1.0",
22 "minimum_chrome_version": "10.0",
23 <b>"devtools_page": "devtools.html"</b>,
24 ...
25 }
26 </pre>
27 </li>
28 <li>
29 An instance of the devtools_page specified in your extension's manifest
30 will be created for every Developer Tools window opened. The page may add
31 other extension pages as panels and sidebars to the Developer Tools window
32 using <a href="devtools.panels.html">devtools.panels</a>
33 API.
34 </li>
35 <li>
36 The chrome.devtools.* API modules are available only to the
37 pages loaded within the Developer Tools window. Content scripts and other
38 extension pages do not have these APIs. Thus, the APIs are available only
39 through the lifetime of the Developer Tools window.
40 </li>
41 <li>The APIs available to extension pages within the Developer Tools
42 window include all <a href="#api-list">devtools modules
43 listed above</a> and <a href="extension.html">chrome.extension</a> API.
44 Other extension APIs are not available to the Developer Tools pages, but
45 you may invoke them by sending a request to the background page of your
46 extension, similarly to how it's done in the
47 <a href="overview.html#contentScripts">content scripts</a>.
48 </li><li>
49 There are also some Developer Tools APIs that are still experimental.
50 Please refer to <a href="experimental.html">chrome.experimental.* APIs</a>
51 for the list of experimental APIs and guidelines on how to use them.
52 </li>
53 <li>
54 <a href="http://groups.google.com/group/google-chrome-developer-tools/topics ">Give us feedback!</a>
55 Your comments and suggestions help us improve the APIs.
56 </li>
57 </ol>
58
59 <h2 id="other">More information</h2>
60
61 <p>
62 For information on the standard APIs that extensions can use, see
63 <a href="api_index.html">chrome.* APIs</a> and
64 <a href="api_other.html">Other APIs</a>.
65 </p>
66
67 <h2 id="examples">Examples</h2>
68
69 <p>
70 You can find examples that use Developer Tools APIs in
71 <a href="samples.html#devtools">Samples</a>.
72 </p>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698