1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
|
<!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note:
1) The <head> information in this page is significant, should be uniform
across api docs and should be edited only with knowledge of the
templating mechanism.
3) All <body>.innerHTML is genereated as an rendering step. If viewed in a
browser, it will be re-generated from the template, json schema and
authored overview content.
4) The <body>.innerHTML is also generated by an offline step so that this
page may easily be indexed by search engines.
--><html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link href="css/ApiRefStyles.css" rel="stylesheet" type="text/css">
<script type="text/javascript" src="../../../third_party/jstemplate/jstemplate_compiled.js">
</script>
<script type="text/javascript" src="js/api_page_generator.js"></script>
<script type="text/javascript" src="js/bootstrap.js"></script>
<title>Overview</title></head><body> <div id="container">
<!-- SUBTEMPLATES: DO NOT MOVE FROM THIS LOCATION -->
<!-- In particular, sub-templates that recurse, must be used by allowing
jstemplate to make a copy of the template in this section which
are not operated on by way of the jsskip="true" -->
<div style="display:none">
<!-- VALUE -->
<div id="valueTemplate">
<dt>
<var>paramName</var>
<em>
<!-- TYPE -->
<div style="display:inline">
(
<span class="optional">optional</span>
<span id="typeTemplate">
<span>
<a> Type</a>
</span>
<span>
<span>
array of <span><span></span></span>
</span>
<span>paramType</span>
</span>
</span>
)
</div>
</em>
</dt>
<dd class="todo">
Undocumented.
</dd>
<dd>
Description of this parameter from the json schema.
</dd>
<!-- OBJECT PROPERTIES -->
<dd>
<dl>
<div>
<div>
</div>
</div>
</dl>
</dd>
</div> <!-- /VALUE -->
</div> <!-- /SUBTEMPLATES -->
<a name="top"> </a>
<!-- API HEADER -->
<div id="pageHeader">
<div id="searchbox">
<form action="http://www.google.com/cse" id="cse-search-box">
<div>
<input type="hidden" name="cx" value="002967670403910741006:61_cvzfqtno">
<input type="hidden" name="ie" value="UTF-8">
<input type="text" name="q" size="31">
<input type="submit" name="sa" value="Search">
</div>
</form>
<script type="text/javascript" src="http://www.google.com/jsapi"></script>
<script type="text/javascript">google.load("elements", "1", {packages: "transliteration"});</script>
<script type="text/javascript" src="http://www.google.com/coop/cse/t13n?form=cse-search-box&t13n_langs=en"></script>
<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>
</div>
<div id="pageTitle">
<h1>Overview</h1>
</div>
</div> <!-- /pageHeader -->
<div id="pageContent">
<!-- SIDENAV -->
<div id="leftNav">
<ul>
<li> <a href="index.html">Home</a></li>
<li> <a href="getstarted.html">Getting Started</a></li>
<li class="leftNavSelected">Overview </li>
<li> <a href="devguide.html"><div>Developer's Guide</div></a>
<ul>
<li><a href="toolstrip.html">Toolstrips</a></li>
<li><a href="pageActions.html">Page Actions</a></li>
<li><a href="background_pages.html">Background Pages</a></li>
<li><a href="content_scripts.html">Content Scripts</a></li>
<li><a href="events.html">Events</a></li>
<li><a href="tabs.html">Tabs</a></li>
<li><a href="windows.html">Windows</a></li>
<li><a href="bookmarks.html">Bookmarks</a></li>
<li><a href="themes.html">Themes</a></li>
<li><a href="npapi.html">NPAPI Plugins</a></li>
<li><a href="xhr.html">Cross-Origin XHR</a></li>
<li><a href="packaging.html">Packaging</a></li>
<li><a href="autoupdate.html">Autoupdate</a></li>
</ul>
</li>
<li><a href="tutorials.html"><div>Tutorials</div></a>
<ul>
<li><a href="tut_debugging.html">Debugging</a></li>
</ul>
</li>
<li>Reference
<ul>
<li> Formats
<ul>
<li><a href="manifest.html">Manifest Files</a></li>
<li><a href="match_patterns.html">Match Patterns</a></li>
<li>Packages (.crx)</li>
</ul>
</li>
<li> <a href="api_index.html">chrome.* APIs</a> </li>
<li> <a href="api_other.html">Other APIs</a> </li>
</ul>
</li>
<li><a href="http://dev.chromium.org/developers/design-documents/extensions/samples">Samples</a></li>
</ul>
</div>
<div id="mainColumn">
<!-- TABLE OF CONTENTS -->
<div id="toc">
<p>Contents</p>
<ol>
<li jsinstance="0">
<a href="#what">The basics</a>
<ol>
<li jsinstance="*0" style="display: none; ">
<a>h3Name</a>
</li>
</ol>
</li><li jsinstance="1">
<a href="#files">Files</a>
<ol>
<li jsinstance="0">
<a href="#H3-2">Referring to files</a>
</li><li jsinstance="*1">
<a href="#H3-3">The manifest file</a>
</li>
</ol>
</li><li jsinstance="2">
<a href="#arch">Architecture</a>
<ol>
<li jsinstance="0">
<a href="#background">The background page</a>
</li><li jsinstance="*1">
<a href="#contentScripts">Content scripts</a>
</li>
</ol>
</li><li jsinstance="3">
<a href="#H2-7">Communication </a>
<ol>
<li jsinstance="*0" style="display: none; ">
<a>h3Name</a>
</li>
</ol>
</li><li jsinstance="*4">
<a href="#H2-8"> Summary </a>
<ol>
<li jsinstance="*0" style="display: none; ">
<a>h3Name</a>
</li>
</ol>
</li>
<div style="display: none; ">
<li>
<a href="#apiReference">API reference</a>
<ol>
<li>
<a href="#properties">Properties</a>
<ol>
<li>
<a href="#property-anchor">propertyName</a>
</li>
</ol>
</li>
<li>
<a href="#methods">Methods</a>
<ol>
<li>
<a href="#method-anchor">methodName</a>
</li>
</ol>
</li>
<li>
<a href="#events">Events</a>
<ol>
<li>
<a href="#event-anchor">eventName</a>
</li>
</ol>
</li>
<li>
<a href="#types">Types</a>
<ol>
<li>
<a href="#id-anchor">id</a>
</li>
</ol>
</li>
</ol>
</li>
</div>
</ol>
</div>
<!-- /TABLE OF CONTENTS -->
<!-- STATIC CONTENT PLACEHOLDER -->
<div id="static"><div id="pageData-title" class="pageData">Overview</div>
<div id="pageData-showTOC" class="pageData">true</div>
<p>
Please read this page;
it has vital information about the extension architecture.
If you get bored or restless,
take a break!
We suggest bouncing between this page
and tutorials
such as <a href="getstarted.html">Getting Started</a>
and <a href="tut_debugging.html">Debugging</a>.
</p>
<h2 id="what">The basics</h2>
<p>
An extension is a zipped bundle of files —
HTML, CSS, JavaScript, images, and anything else you need —
that adds functionality to the Google Chrome browser.
Because an extension is just a special kind of web page,
it can use all the APIs
that the browser provides
to web pages and apps,
from XMLHttpRequest to JSON to localStorage.
</p>
<p>
Extensions can add UI to Google Chrome,
in the form of
<a href="toolstrip.html">toolstrips</a> (toolbar additions)
and <a href="pageActions.html">page actions</a>
(clickable badges in the address bar).
Extensions can also interact programmatically
with browser features such as
<a href="bookmarks.html">bookmarks</a>
and <a href="tabs.html">tabs</a>.
</p>
<p>
To find a complete list of extension features,
with implementation details
for each one,
see the <a href="devguide.html">Developer's Guide</a>.
</p>
<h2 id="files">Files</h2>
<p>
Each extension has the following files:
<!-- PENDING: This could use a picture -->
</p>
<ul>
<li>A <b>manifest file</b></li>
<li>One or more <b>HTML files</b> (unless the extension is a theme)</li>
<li><em>Optional:</em> One or more <b>JavaScript files</b></li>
<li><em>Optional:</em> Any other files your extension needs — for example, image files</li>
</ul>
<p>
While you're working on your extension,
you put all these files into a single folder.
When you distribute your extension,
the contents of the folder are packaged into a special zipfile
that has a <code>.crx</code> suffix,
as described in <a href="packaging.html">Packaging</a>.
</p>
<a name="H3-2"></a><h3>Referring to files</h3>
<p>
You can put any file you like into an extension,
but how do you use it?
Usually,
you can refer to the file using a relative URL,
just as you would in an ordinary HTML page.
Here's an example of referring to
a file named <code>myimage.png</code>
that's in a subfolder named <code>images</code>.
</p>
<pre><img <b>src="images/myimage.png"</b> style="width:auto; height:auto">
</pre>
<p>
As you might notice while you use the Google Chrome debugger,
every file in an extension is also accessible by an absolute URL like this:
</p>
<blockquote>
<b>chrome-extension://</b><em><extensionID></em><b>/</b><em><pathToFile></em>
</blockquote>
<p>
In that URL, the <em><extensionID></em> is a unique identifier
that the extension system generates for each extension.
You can see the IDs for all your loaded extensions
by going to the URL <b>chrome://extensions/</b>.
The <em><pathToFile></em> is the location of the file
under the extension's top folder;
it's the same as the relative URL.
</p>
<p>
For example, assume your extension has
the ID <b>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</b>
and the files shown in the following figure:
</p>
<pre><span class="tbd">[PENDING: someday this will be a real figure]</span>
toolstrip.html
styles.css
images:
myimage.png
...
other:
more.html
morestyles.css
...
</pre>
<p>
Here's a table that shows the relative and absolute URLs of these files.
Keep in mind that the relative URL is the same no matter where you're using it —
the relative URL of <code>myimage.png</code> is
<b>images/myimage.png</b>,
no matter whether it's being used by
<code>toolstrip.html</code> or <code>other/more.html</code>.
</p>
<table>
<tbody><tr>
<th> File </th>
<th> Relative URL </th>
<th> Absolute URL </th>
</tr>
<tr>
<td> toolstrip.html </td>
<td> toolstrip.html </td>
<td> chrome-extension://aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/toolstrip.html </td>
</tr>
<tr>
<td> styles.css </td>
<td> styles.css </td>
<td> chrome-extension://aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/styles.css </td>
</tr>
<tr>
<td> myimage.png </td>
<td> images/myimage.png </td>
<td> chrome-extension://aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/images/myimage.png </td>
</tr>
<tr>
<td> more.html </td>
<td> other/more.html </td>
<td> chrome-extension://aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/other/more.html </td>
</tr>
<tr>
<td> morestyles.css </td>
<td> other/morestyles.css </td>
<td> chrome-extension://aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/other/morestyles.css </td>
</tr>
</tbody></table>
<p class="tbd">
[PENDING: Mention/reflect/link to
<a href="http://dev.chromium.org/developers/design-documents/extensions/i18n">internationalization</a>]
</p>
<a name="H3-3"></a><h3>The manifest file</h3>
<p>
The manifest file, called <code>manifest.json</code>,
gives information about the extension,
such as the most important files
and the capabilities that the extension might use.
Here's a typical manifest file for a toolstrip
that uses information from google.com:
</p>
<pre>{
"name": "My Extension",
"version": "2.1",
"description": "Gets information from Google.",
"update_url": "http://example.com/mytestextension/updates.xml",
"permissions": ["http://*.google.com/", "https://*.google.com/"],
"toolstrips": ["my_toolstrip.html"]
}</pre>
<p>
For details, see
<a href="manifest.html">Manifest Files</a>.
</p>
<h2 id="arch">Architecture</h2>
<p>
The following pictures shows the web pages associated with a typical extension
(in this case, a simple toolstrip).
The first figure shows what an extension might look like
when there's a single browser window.
</p>
<p class="tbd"> [PENDING: image goes here] </p>
<p>
The next figure shows that all the code in the extension's main HTML file
is duplicated each time you create a new window.
In other words, each window has its own widgets for the extension,
which means each window adds another web page for that extension.
</p>
<p class="tbd"> [PENDING: image goes here] </p>
<p>
To more easily coordinate all these web pages and to avoid duplication,
you should design your extension
so that most of the code —
especially the state of the extension —
is in a <em>background page</em>,
as shown in the following figure.
</p>
<p class="tbd"> [PENDING: image goes here] </p>
<h3 id="background">The background page</h3>
<p>
Any non-trivial extension can (and probably should)
have a background page.
The background page is an invisible page
where you put the main logic of the extension.
The extension's other pages should have
only the code that's necessary
to show the state of the extension
and to get input from the user.</p>
<p>
An extension's background page exists
before any of the extension's other pages exist.
It continues to exist as long as the browser is running
and the extension is installed,
even if other pages and windows go away.
</p>
<p>
Your extension's UI —
its toolstrips, page actions, and so on —
should be dumb views.
When the view needs some state,
it should request it from the background page.
When the background page notices some state change,
it should update all the views.
</p>
<p>
For more information, see
<a href="background_pages.html">Background Pages</a>.
</p>
<h3 id="contentScripts">Content scripts</h3>
<p>
If you want your extension to interact with web pages,
you need a content script.
Content scripts are JavaScript files that run in the context of web pages.
By using the standard Document Object Model (DOM),
they can read details of the web pages the browser visits,
and they can make changes to the pages.
</p>
<p class="comment">
[PENDING: add an architectural figure here,
showing the extension's pages, a web page, and the content script
interacting with the web page. explain the figure.]
</p>
<p>
For more information,
see <a href="content_scripts.html">Content Scripts</a>.
</p>
<a name="H2-7"></a><h2>Communication </h2>
<p>
Two kinds of communication happen within an extension:
</p>
<ul>
<li>
Communication <b>between pages</b> in the extension.
<br>
For example, sometimes the background page
needs to update all the UI pages
to reflect a change in the extension's state.
</li>
<li>
Communication <b>between content scripts and the extension</b>.
<br>
For example,
<span class="tbd">[PENDING: typical use case goes here]</span>.
See <a href="content_scripts.html">Content Scripts</a>
for information about this type of communication.
</li>
</ul>
<p>
Here are some keys to communication between an extension's pages:
</p>
<ul>
<li>
All the extension's pages execute in same process,
on the same thread.
</li>
<li>
Extension pages can use
<a href="extension.html"><code>chrome.extension</code></a>
methods such as
<code>getViews()</code>,
<code>getBackgroundPage()</code>,
and <code>getToolstrips()</code>
to get access to the extension's pages.
</li>
<li>
Once you have references to an extension's pages,
you can manipulate the DOM for each page.
</li>
<li>
You can also make direct function calls to the pages,
as shown in the following example.
</li>
</ul>
<p>
Here's an example of
communication between toolstrips and the background page.
</p>
<pre>//In background_page.html:
function updateUI(checked) {
var toolstrips = chrome.extension.getToolstrips();
for (var i in toolstrips) {
if (toolstrips[i].enableCheckbox)
toolstrips[i].enableCheckbox(checked);
}
}
//In toolstrip.html:
function enableCheckbox(checked) {
var cb = document.getElementById('checkbox');
cb.checked = checked;
}
</pre>
<p>
A good summary of communication mechanisms is at
<a href="http://www.chromeplugins.org/google/plugins-development/communication-7883.html">http://www.chromeplugins.org/google/plugins-development/communication-7883.html</a>.
</p>
<a name="H2-8"></a><h2> Summary </h2>
<p class="tbd">
[
PENDING: summarize, suggest where to go next. Probably:
<a href="getstarted.html">Getting Started</a>,
<a href="tut_debugging.html">Debugging</a>,
<a href="devguide.html">Developer's Guide</a>.
]
</p>
</div>
<!-- API PAGE -->
<div class="apiPage" style="display: none; ">
<a name="apiReference"></a>
<h2>API reference: chrome.apiname </h2>
<!-- PROPERTIES -->
<div class="apiGroup">
<a name="properties"></a>
<h3 id="properties">Properties</h3>
<div>
<a></a>
<h4>getLastError</h4>
<div class="summary">
<!-- Note: intentionally longer 80 columns -->
<span>chrome.extension</span><span>lastError</span>
</div>
<div>
</div>
</div>
</div> <!-- /apiGroup -->
<!-- METHODS -->
<div class="apiGroup" id="methods">
<a name="methods"></a>
<h3>Methods</h3>
<!-- iterates over all functions -->
<div class="apiItem">
<a></a> <!-- method-anchor -->
<h4>method name</h4>
<div class="summary"><span>void</span>
<!-- Note: intentionally longer 80 columns -->
<span>chrome.module.methodName</span>(<span><span>, </span><span></span>
<var><span></span></var></span>)</div>
<div class="description">
<p class="todo">Undocumented.</p>
<p>
A description from the json schema def of the function goes here.
</p>
<!-- PARAMETERS -->
<h4>Parameters</h4>
<dl>
<div>
<div>
</div>
</div>
</dl>
<!-- RETURNS -->
<h4>Returns</h4>
<dl>
<div>
<div>
</div>
</div>
</dl>
<!-- CALLBACK -->
<div>
<div>
<h4>Callback function</h4>
<p>
If you specify the <em>callback</em> parameter,
it should specify a function that looks like this:
</p>
<!-- Note: intentionally longer 80 columns -->
<pre>function(<span>Type param1, Type param2</span>) <span class="subdued">{...}</span>);</pre>
<dl>
<div>
<div>
</div>
</div>
</dl>
</div>
</div>
</div> <!-- /description -->
</div> <!-- /apiItem -->
</div> <!-- /apiGroup -->
<!-- EVENTS -->
<div class="apiGroup">
<a name="events"></a>
<h3 id="events">Events</h3>
<!-- iterates over all events -->
<div class="apiItem">
<a></a>
<h4>event name</h4>
<div class="summary">
<!-- Note: intentionally longer 80 columns -->
<span class="subdued">chrome.bookmarks</span><span>onEvent</span><span class="subdued">.addListener</span>(function(<span>Type param1, Type param2</span>) <span class="subdued">{...}</span>);
</div>
<div class="description">
<p class="todo">Undocumented.</p>
<p>
A description from the json schema def of the event goes here.
</p>
<!-- PARAMETERS -->
<h4>Parameters</h4>
<dl>
<div>
<div>
</div>
</div>
</dl>
</div> <!-- /decription -->
</div> <!-- /apiItem -->
</div> <!-- /apiGroup -->
<!-- TYPES -->
<div class="apiGroup">
<a name="types.sort(sortByName)"></a>
<h3 id="types">Types</h3>
<!-- iterates over all types -->
<div class="apiItem">
<a></a>
<h4>type name</h4>
<div>
</div>
</div> <!-- /apiItem -->
</div> <!-- /apiGroup -->
</div> <!-- /apiPage -->
</div> <!-- /mainColumn -->
</div> <!-- /pageContent -->
<div id="pageFooter" --="">
<p>
Except as otherwise <a href="http://code.google.com/policies.html#restrictions">noted</a>,
the content of this page is licensed under the <a rel="license" href="http://creativecommons.org/licenses/by/3.0/">Creative Commons
Attribution 3.0 License</a>, and code samples are licensed under the
<a rel="license" href="http://code.google.com/google_bsd_license.html">BSD License</a>.
</p>
<p>
©2009 Google
</p>
</div> <!-- /pageFooter -->
</div> <!-- /container -->
</body></html>
|
