Skip to content

GitLab

T
tangled
Commit 2f8a532c authored by crystallambert@chromium.org's avatar crystallambert@chromium.org Committed by Commit Bot
Browse files
Options

[Extension Docs]Overview Update 

Updated language and concept in extension overview document.

Bug: None
Change-Id: I02409acdeabd8597aa01be164dbcf8f316779f84
Reviewed-on: https://chromium-review.googlesource.com/1070320
Commit-Queue: Crystal Lambert <crystallambert@chromium.org>
Reviewed-by: default avatarDevlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565427}
parent 427a4144
Show whitespace changes
Inline Side-by-side
Showing with 283 additions and 451 deletions
chrome/common/extensions/docs/templates/articles/overview.html
View file @ 2f8a532c
<h1>Overview</h1>
<p>
Extensions are zipped bundles of HTML, CSS, JavaScript, images,
and other files used in the web platform,
that customize the Google Chrome browsing experience.
Extensions are built using web technology
and can use the same APIs
the browser provides to the open web.
</p>
<p>
Once you've finished this page
and the
<a href="getstarted">Getting Started</a> tutorial,
you'll be all set to start writing extensions.
Extensions have a wide range of functional possibilities.
They can modify web content users see
and interact with or
extend and change the behavior of the browser itself.
</p>
<h2 id="what">The basics</h2>
<p>
Consider extensions the gateway to making the Chrome browser
the most personalized browser.
</a>
<h2 id="files">Extension Files</h2>
<p>
An extension is a zipped bundle of files&mdash;HTML,
CSS, JavaScript, images, and anything else you need&mdash;that
adds functionality to the Google Chrome browser.
Extensions are essentially web pages,
and they can use all the
<a href="api_other">APIs that the browser provides to web pages</a>,
from XMLHttpRequest to JSON to HTML5.
Extensions vary in types of files and amount of directories,
but they are all required to have a
<a href="extensions/manifest">manifest</a>.
Some basic, but useful,
extensions may consist of just the manifest and its toolbar icon.
</p>
<p>
Extensions can interact with web pages or servers using
<a href="content_scripts">content scripts</a> or
<a href="xhr">cross-origin XMLHttpRequests</a>.
Extensions can also interact programmatically
with browser features such as
<a href="bookmarks">bookmarks</a>
and <a href="tabs">tabs</a>.
The manifest file, titled <code>manifest.json</code>,
gives the browser information about the extension,
such as the most important files and the capabilities the extension might use.
</p>
<h3 id="extension-ui">Extension UIs</h3>
<pre data-filename="manifest.json">
{
"name": "My Extension",
"version": "2.1",
"description": "Gets information from Google.",
"icons": {
"128": "icon_16.png",
"128": "icon_32.png",
"128": "icon_48.png",
"128": "icon_128.png"
},
"background": {
"persistent": false,
"scripts": ["background_script.js"]
},
"permissions": ["https://*.google.com/", "activeTab"],
"browser_action": {
"default_icon": "icon_16.png",
"default_popup": "popup.html"
}
}
</pre>
<p>
Many extensions&mdash;but not Chrome Apps&mdash;add
UI to Google Chrome in the form of
<a href="browserAction">browser actions</a>
or <a href="pageAction">page actions</a>.
Each extension can have at most one browser action or page action.
Choose a <b>browser action</b> when the extension is relevant to most pages.
Choose a <b>page action</b> when the extension's icon
should be active or inactive (and grayed out),
depending on the page.
Extensions must have an icon that sits in the browser toolbar.
Toolbar icons allow easy access and
keep users aware of which extensions are installed.
Most users will interact with an extension that uses a
<a href="user_interface#popup">popup</a> by clicking on the icon.
</p>
<table class="simple">
<tr>
<tr>
<td width="33%">
<img src="{{static}}/images/overview/browser_arrow.png"
width="102" height="90"
......@@ -56,442 +79,260 @@ depending on the page.
width="79" height="90"
alt="screenshot" />
</td>
</tr>
<tr>
<td>
<img src="{{static}}/images/overview/page_color.png"
width="107" height="90"
alt="screenshot" />
</td>
</tr>
<tr>
<td>
This <a href="samples#google-mail-checker">Google Mail Checker extension</a>
uses a <em>browser action</em>.
</td>
<td>
This <a href="samples#mappy">Mappy extension</a>
uses a <em>page action</em>
and <em>content script</em>
(code injected into a web page).
This <a href="/extensions/samples#search:google%20mail%20checker">
Google Mail Checker extension</a>
uses a <a href="browserAction">browser action</a>.
</td>
<td>
This <a href="samples#set_page_color">Set Page Color extension</a>
features a browser action that,
when clicked,
shows a <em>popup</em>.
This <a href="/extensions/samples#search:mappy">Mappy extension</a>
uses a <a href="pageAction">page action</a>
and <a href="#contentScripts">content script</a>.
</td>
</tr>
</tr>
</table>
<p>
Extensions (and Chrome Apps) can also present a UI in other ways,
such as adding to the Chrome context menu,
providing an options page,
or using a content script that changes how pages look.
See the <a href="devguide">Developer's Guide</a>
for a complete list of extension features,
with links to implementation details
for each one.
</p>
<h2 id="files">Files</h2>
<p>
Each extension has the following files:
</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&mdash;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 ZIP file
that has a <code>.crx</code> suffix.
If you upload your extension using the
<a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Developer Dashboard</a>,
the <code>.crx</code> file is created for you.
For details on distributing extensions,
see <a href="hosting">Hosting</a>.
</p>
<h3 id="relative-urls">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>.
An extension's files can be referred to by using a relative URL,
just as files in an ordinary HTML page.
</p>
<pre>
&lt;img <b>src="images/myimage.png"</b>>
&lt;img <b>src="images/my_image.png"</b>>
</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:
Additionally, each file can also be accessed using an absolute URL.
</p>
<blockquote>
<b>chrome-extension://</b><em>&lt;extensionID></em><b>/</b><em>&lt;pathToFile></em>
<b>chrome-extension://</b><em>&lt;extensionID&gt;</em><b>/</b><em>&lt;pathToFile&gt;</em>
</blockquote>
<p>
In that URL, the <em>&lt;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>&lt;pathToFile></em> is the location of the file
under the extension's top folder;
it's the same as the relative URL.
</p>
<p>
While you're working on an extension
(before it's packaged),
the extension ID can change.
Specifically, the ID of an unpacked extension will change
if you load the extension from a different directory;
the ID will change again when you package the extension.
If your extension's code
needs to specify the full path to a file within the extension,
you can use the <code>@@extension_id</code>
<a href="i18n#overview-predefined">predefined message</a>
to avoid hardcoding the ID during development.
</p>
<p>
When you package an extension
(typically, by uploading it with the dashboard),
the extension gets a permanent ID,
which remains the same even after you update the extension.
Once the extension ID is permanent,
you can change all occurrences of
<code>@@extension_id</code> to use the real ID.
</p>
<h3 id="manifest">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 browser action
that uses information from google.com:
In the absolute URL, the <em>&lt;extensionID&gt;</em> is a unique identifier
that the extension system generates for each extension.
The IDs for all loaded extensions can be viewed
by going to the URL <b>chrome://extensions</b>.
The <em>&lt;pathToFile&gt;</em> is the location of the file
under the extension's top folder;
it matches the relative URL.
</p>
<pre data-filename="manifest.json">
{
"name": "My Extension",
"version": "2.1",
"description": "Gets information from Google.",
"icons": { "128": "icon_128.png" },
"background": {
"persistent": false,
"scripts": ["bg.js"]
},
"permissions": ["http://*.google.com/", "https://*.google.com/"],
"browser_action": {
"default_title": "",
"default_icon": "icon_19.png",
"default_popup": "popup.html"
}
}</pre>
<p>
For details, see
<a href="manifest">Manifest Files</a>.
While working on an unpacked extension
the extension ID can change.
Specifically, the ID of an unpacked extension will change
if the extension is loaded from a different directory;
the ID will change again when the extension is packaged.
If an extension's code relies on an absolute URL,
it can use the
<a href="extensions/runtime#method-getURL">
<code>chrome.runtime.getURL()</code>
</a>
method to avoid hardcoding the ID during development.
</p>
<h2 id="arch">Architecture</h2>
<p>
Many extensions have a <em>background page</em>,
an invisible page
that holds the main logic of the extension.
An extension can also contain other pages
that present the extension's UI.
If an extension needs to interact with web pages that the user loads
(as opposed to pages that are included in the extension),
then the extension must use a content script.
An extension’s architecture will depend on its functionality,
but many robust extensions will include multiple components:
</p>
<ul>
<li>
<a href="extensions/manifest">Manifest</a>
</li>
<li>
<a href="#background_script">Background Script</a>
</li>
<li>
<a href="#pages">UI Elements</a>
</li>
<li>
<a href="#contentScripts">Content Script</a>
</li>
<li>
<a href="#optionsPage">Options Page</a>
</li>
</ul>
<h3 id="background_page">The background page</h3>
<p>
Background pages defined by <code>background.html</code>
can include JavaScript code that controls
the behavior of the extension.
There are two types of background pages:
<a href="background_pages">persistent background pages</a>,
and <a href="event_pages">event pages</a>. Persistent
background pages, as the name suggests, are always open.
Event pages are opened and closed as needed. Unless you absolutely
need your background page to run all the time, prefer to use
an event page.
</p>
<!-- PENDING: Perhaps show a picture of many background page processes.
This could build on a figure that shows the process architecture. -->
<h3 id="background_script">Background Script</h3>
<p>
See <a href="event_pages">Event Pages</a>
and <a href="background_pages">Background Pages</a>
for more details.
The <a href="/background_pages">background script</a> is the extension's
event handler; it contains listeners
for browser events that are important to the extension.
It lies dormant until an event is fired then performs the instructed logic.
An effective background script is only loaded when it is needed
and unloaded when it goes idle.
</p>
<h3 id="pages">UI pages</h3>
<h3 id="pages">UI Elements</h3>
<p>
Extensions can contain ordinary HTML pages that display the extension's UI.
For example, a browser action can have a popup,
which is implemented by an HTML file.
Any extension can have an options page,
which lets users customize how the extension works.
Another type of special page is the override page.
And finally, you can
use $(ref:tabs.create)
or <code>window.open()</code>
to display any other HTML files that are in the extension.
An <a href="user_interface">extension's user interface</a>
should be purposeful and minimal.
The UI should customize or enhance the browsing experience
without distracting from it.
Most extensions have a <a href="browserAction">browser action</a> or
<a href="pageAction">page action</a>,
but can contain other forms of UI,
such as <a href="/contextMenus">context menus</a>,
use of the <a href="omniBox">omnibox</a>,
or creation of a <a href="commands">keyboard shortcut</a>.
</p>
<p>
The HTML pages inside an extension
have complete access to each other's DOMs,
and they can invoke functions on each other.
</p>
<!-- PENDING: Change the following example and figure
to use something that's not a popup?
(It might lead people to think that popups need background pages.) -->
<p>
The following figure shows the architecture
of a browser action's popup.
The popup's contents are a web page
defined by an HTML file
(<code>popup.html</code>).
This extension also happens to have a background page
(<code>background.html</code>).
The popup doesn't need to duplicate code
that's in the background page
because the popup can invoke functions on the background page.
Extension UI pages,
such as a <a href="user_interface#popup">popup</a>,
can contain ordinary HTML pages with JavaScript logic.
Extensions can also call <a href="tabs#method-create">tabs.create</a> or
<code>window.open()</code> to display additional HTML files present
in the extension.
</p>
<img src="{{static}}/images/overview/arch-2.gif"
width="256" height="168"
alt="A browser window containing a browser action that's displaying a popup. The popup's HTML file (popup.html) can communicate with the extension's background page (background.html)." />
<p>
See <a href="browserAction">Browser Actions</a>,
<a href="options">Options</a>,
<a href="override">Override Pages</a>,
and the <a href="#pageComm">Communication between pages</a> section
for more details.
An extension using a page action and a popup
can use the <a href="declarativeContent">declarative content</a> API to set
rules in the background script
for when the popup is available to users.
When the conditions are met,
the background script communicates with the popup
to make it’s icon clickable to users.
</p>
<img src="{{static}}/images/overview/popuparc.png"
alt="A browser window containing a page action displaying a popup." />
<h3 id="contentScripts">Content scripts</h3>
<p>
If your extension needs to interact with web pages,
then it needs a <em>content script</em>.
A content script is some JavaScript
that executes in the context of a page
that's been loaded into the browser.
Think of a content script as part of that loaded page,
not as part of the extension it was packaged with
(its <em>parent extension</em>).
</p>
<!-- [PENDING: Consider explaining that the reason content scripts are separated from the extension is due to chrome's multiprocess design. Something like:
Each extension runs in its own process.
To have rich interaction with a web page, however,
the extension must be able to
run some code in the web page's process.
Extensions accomplish this with content scripts.]
-->
<p>
Content scripts can read details of the web pages the browser visits,
and they can make changes to the pages.
In the following figure,
the content script
can read and modify
the DOM for the displayed web page.
It cannot, however, modify the DOM of its parent extension's background page.
Extensions that read or write to web pages utilize a
<a href="content_scripts">content script</a>.
The content script contains JavaScript that executes in the contexts of a page
that has been loaded into the browser.
Content scripts read and modify the DOM of web pages the browser visits.
</p>
<img src="{{static}}/images/overview/arch-3.gif"
width="238" height="169"
alt="A browser window with a browser action (controlled by background.html) and a content script (controlled by contentscript.js)." />
<img src="{{static}}/images/overview/contentscriptarc.png"
alt="A browser window with a page action and a content script." />
<p>
Content scripts aren't completely cut off from their parent extensions.
A content script can exchange messages with its parent extension,
as the arrows in the following figure show.
For example, a content script might send a message
whenever it finds an RSS feed in a browser page.
Or a background page might send a message
asking a content script to change the appearance of its browser page.
Content scripts can communicate with their parent extension
by exchanging <a href="messaging">messages</a> and storing values using the
<a href="storage">storage</a> API.
</p>
<img src="{{static}}/images/overview/arch-cs.gif"
width="238" height="194"
alt="Like the previous figure, but showing more of the parent extension's files, as well as a communication path between the content script and the parent extension." />
<img src="{{static}}/images/overview/messagingarc.png"
alt="Shows a communication path between the content script and the parent extension." />
<h3 id="optionsPage">Options Page</h3>
<p>
For more information,
see <a href="content_scripts">Content Scripts</a>.
Just as extensions allow users to customize the Chrome browser,
the <a href="options">options page</a> enables customization of the extension.
Options can be used to enable features and allow users
to choose what functionality is relevant to their needs.
</p>
<h2 id="apis"> Using the chrome.* APIs </h2>
<h2 id="apis">Using Chrome APIs</h2>
<p>
In addition to having access to all the APIs that web pages and apps can use,
extensions can also use Chrome-only APIs
(often called <em>chrome.* APIs</em>)
that allow tight integration with the browser.
For example, any extension or web app can use the
standard <code>window.open()</code> method to open a URL.
But if you want to specify which window that URL should be displayed in,
your extension can use the Chrome-only
$(ref:tabs.create)
method instead.
In addition to having access to the same APIs as web pages,
extensions can also use <a href="api_index">extension-specific APIs</a>
that create tight integration with the browser.
Extensions and webpages can both access the standard
<code>window.open()</code> method to open a URL,
but extensions can specify which window that URL should be displayed in
by using the Chrome API <a href="tabs#method-create">tabs.create</a>
method instead.
</p>
<h3 id="sync"> Asynchronous vs. synchronous methods </h3>
<p>
Most methods in the chrome.* APIs are <b>asynchronous</b>:
they return immediately, without waiting for the operation to finish.
If you need to know the outcome of that operation,
then you pass a callback function into the method.
That callback is executed later (potentially <em>much</em> later),
sometime after the method returns.
Here's an example of the signature for an asynchronous method:
Most Chrome API methods are asynchronous:
they return immediately without waiting for the operation to finish.
If an extension needs to know the outcome of an asynchronous operation
it can pass a callback function into the method.
The callback is executed later, potentially much later,
after the method returns.
</p>
<p>
<code>
chrome.tabs.create(object <em>createProperties</em>, function <em>callback</em>)
</code>
If the extension needed to navigate the user’s currently selected tab
to a new URL, it would need to get the current tab’s ID
and then update that tab’s address to the new URL.
</p>
<p>
Other chrome.* methods are <b>synchronous</b>.
Synchronous methods never have a callback
because they don't return until they've completed all their work.
Often, synchronous methods have a return type.
Consider the
$(ref:runtime.getURL) method:
If the <a href="/tabs#method-query">tabs.query</a> method were synchronous,
it may look something like below.
</p>
<p>
<code>
string chrome.runtime.getURL()
</code>
</p>
<pre>
<b>//THIS CODE DOESN'T WORK</b>
var tab = chrome.tabs.query({'active': true}); <b>//WRONG!!!</b>
chrome.tabs.update(tab.id, {url:newUrl});
someOtherFunction();
</pre>
<p>
This method has no callback and a return type of <code>string</code>
because it synchronously returns the URL
and performs no other, asynchronous work.
This approach will fail because <code>query()</code> is asynchronous.
It returns without waiting for the work to complete,
and does not return a value.
A method is asynchronous when the callback parameter is available
in its signature.
</p>
<h3 id="sync-example"> Example: Using a callback </h3>
<p>
Say you want to navigate
the user's currently selected tab to a new URL.
To do this, you need to get the current tab's ID
(using $(ref:tabs.query))
and then make that tab go to the new URL
(using $(ref:tabs.update)).
</p>
<pre>
// Signature for an asynchronous method
chrome.tabs.query(object <em>queryInfo</em>, function <em>callback</em>)
</pre>
<p>
If <code>query()</code> were synchronous,
you might write code like this:
To correctly query a tab and update its URL
the extension must use the callback parameter.
</p>
<pre>
<b>//THIS CODE DOESN'T WORK</b>
var tab = chrome.tabs.query({'active': true}); <b>//WRONG!!!</b>
chrome.tabs.update(tab.id, {url:newUrl});
someOtherFunction();
<b>//THIS CODE WORKS</b>
chrome.tabs.query({'active': true}, <b>function(tabs) {</b>
chrome.tabs.update(tabs[0].id, {url: newUrl});
<b>}</b>);
someOtherFunction();
</pre>
<p>
That approach fails
because <code>query()</code> is asynchronous.
It returns without waiting for its work to complete,
and it doesn't even return a value
(although some asynchronous methods do).
You can tell that <code>query()</code> is asynchronous
by the <em>callback</em> parameter in its signature:
<p>
<code>
chrome.tabs.query(object <em>queryInfo</em>, function <em>callback</em>)
</code>
</p>
<p>
To fix the preceding code,
you must use that callback parameter.
The following code shows
how to define a callback function
that gets the results from <code>query()</code>
(as a parameter named <code>tab</code>)
and calls <code>update()</code>.
In the above code, the lines are executed in the following order: 1, 4, 2.
The callback function specified to <code>query()</code> is called
and then executes line 2,
but only after information about the currently selected tab is available.
This happens sometime after <code>query()</code> returns.
Although <code>update()</code> is asynchronous
the code doesn’t use a callback parameter,
since the extension doesn’t do anything with the results of the update.
</p>
<pre>
<b>//THIS CODE WORKS</b>
chrome.tabs.query({'active': true}, <b>function(tabs) {</b>
chrome.tabs.update(tabs[0].id, {url: newUrl});
<b>}</b>);
someOtherFunction();
// Synchronous methods have no callback option and returns a type of string
<em>string</em> chrome.runtime.getURL()
</pre>
<p>
In this example, the lines are executed in the following order: 1, 4, 2.
The callback function specified to <code>query()</code> is called
(and line 2 executed)
only after information about the currently selected tab is available,
which is sometime after <code>query()</code> returns.
Although <code>update()</code> is asynchronous,
this example doesn't use its callback parameter,
since we don't do anything about the results of the update.
This method synchronously returns the URL as a <code>string</code>
and performs no other asynchronous work.
</p>
<h3 id="chrome-more"> More details </h3>
<p>
For more information, see the
<a href="api_index">chrome.* API docs</a>
and watch this video:
For more information, explore the
<a href="api_index">Chrome API reference docs</a>
and watch the following video.
</p>
<div class="video-container">
......@@ -499,97 +340,88 @@ and watch this video:
</div>
<h2 id="pageComm">Communication between pages </h2>
<p>
The HTML pages within an extension often need to communicate.
Because all of an extension's pages
execute in same process on the same thread,
the pages can make direct function calls to each other.
</p>
<p>
To find pages in the extension, use
<a href="extension"><code>chrome.extension</code></a>
methods such as
<code>getViews()</code> and
<code>getBackgroundPage()</code>.
Once a page has a reference to other pages within the extension,
the first page can invoke functions on the other pages,
and it can manipulate their DOMs.
Different components in an extension
often need to communicate with each other.
Different HTML pages can find each other by using the
<a href="extension"><code>chrome.extension</code></a> methods,
such as <code>getViews()</code> and <code>getBackgroundPage()</code>.
Once a page has a reference to other extension pages
the first one can invoke functions on the other pages
and manipulate their DOMs.
Additionally, all components of the extension can access values stored
using the <a href="storage">storage</a> API
and communicate through <a href="messaging">message passing</a>.
</p>
<h2 id="incognito"> Saving data and incognito mode </h2>
<p>
Extensions can save data using the $(ref:storage) API,
the HTML5 <a href="http://dev.w3.org/html5/webstorage/">web storage API</a>
(such as <code>localStorage</code>)
or by making server requests that result in saving data.
Whenever you want to save something,
first consider whether it's
from a window that's in incognito mode.
By default, extensions don't run in incognito windows.
You need to consider what a user expects
from your extension
when the browser is incognito.
Extensions can save data using the $(ref:storage) API,
the HTML5
<a href="https://html.spec.whatwg.org/multipage/webstorage.html">
web storage API
</a>, or by making server requests that result in saving data.
When the extension needs to save something,
first consider if it's from an incognito window.
By default, extensions don't run in incognito windows.
</p>
<p>
<em>Incognito mode</em> promises that the window will leave no tracks.
When dealing with data from incognito windows,
do your best to honor this promise.
For example, if your extension normally
saves browsing history to the cloud,
don't save history from incognito windows.
On the other hand, you can store
your extension's settings from any window,
incognito or not.
</p>
<p class="note">
<b>Rule of thumb:</b>
If a piece of data might show where a user
has been on the web or what the user has done,
don't store it if it's from an incognito window.
<em>Incognito mode</em> promises that the window will leave no tracks.
When dealing with data from incognito windows,
extensions should honor this promise.
If an extension normally saves browsing history,
don't save history from incognito windows.
However, extensions can store setting preferences from any window,
incognito or not.
</p>
<p>
To detect whether a window is in incognito mode,
check the <code>incognito</code> property of the relevant
$(ref:tabs.Tab) or
$(ref:windows.Window) object.
For example:
To detect whether a window is in incognito mode,
check the <code>incognito</code> property of the relevant
$(ref:tabs.Tab) or
$(ref:windows.Window) object.
</p>
<pre>
function saveTabData(tab, data) {
function saveTabData(tab) {
if (tab.incognito) {
chrome.runtime.getBackgroundPage(function(bgPage) {
bgPage[tab.url] = data; // Persist data ONLY in memory
});
return;
} else {
localStorage[tab.url] = data; // OK to store data
chrome.storage.local.set({data: tab.url});
}
}
</pre>
<h2 id="now-what"> Now what? </h2>
<h2 id="next-steps">Take the Next Step</h2>
<p>
Now that you've been introduced to extensions,
you should be ready to write your own.
Here are some ideas for where to go next:
After reading the overview and
completing the <a href="getstarted">Getting Started</a> tutorial,
developers should be ready to start writing their own extensions!
Dive deeper into the world of custom Chrome with the following resources.
</p>
<ul>
<li> <a href="getstarted">Tutorial: Getting Started</a> </li>
<li> <a href="tut_debugging">Tutorial: Debugging</a> </li>
<li> <a href="devguide">Developer's Guide</a> </li>
<li> <a href="samples">Samples</a> </li>
<li> <a href="http://www.youtube.com/view_play_list?p=CA101D6A85FE9D4B">Videos</a>,
such as
<a href="http://www.youtube.com/watch?v=B4M_a7xejYI&feature=PlayList&p=CA101D6A85FE9D4B&index=6">Extension Message Passing</a>
<li>
<p>
Learn about the options available for debugging Extensions in the
<a href="/extensions/tut_debugging">debugging tutorial</a>.
</p>
</li>
<li>
<p>
Chrome Extensions have access to powerful APIs above and beyond what's
available on the open web.
The <a href="extensions/api_index">chrome.* APIs documentation</a> will
walk through each API.
</p>
</li>
<li>
<p>
The <a href="/devguide">developer's guide</a> has dozens of
additional links to pieces of documentation
relevant to advanced extension creation.
</p>
</li>
</ul>
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment