Extensions Docs Server: Doc conversion script - SVN

chrome/common/extensions/docs/server2/templates/articles/overview.html

-<div id="pageData-name" class="pageData">Overview</div>
-<div id="pageData-showTOC" class="pageData">true</div>
+<h1>Overview</h1>
+
 
 <p>
 Once you've finished this page
 and the
 <a href="getstarted.html">Getting Started</a> tutorial,
 you'll be all set to start writing extensions and packaged apps.
 </p>
 
 <p class="caution">
 <strong>Note:</strong>
@@ skipping 34 matching lines @@
 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 appear or disappear,
 depending on the page.
 </p>
 
 <table class="columns">
 <tr>
   <td width="33%">
-    <img src="../images/overview/browser-action.png"
+    <img src="{{static}}/images/overview/browser-action.png"
       width="147" height="100"
       alt="screenshot" />
   </td>
   <td width="33%">
-    <img src="../images/overview/page-action.png"
+    <img src="{{static}}/images/overview/page-action.png"
       width="147" height="100"
       alt="screenshot" />
   </td>
   <td>
-    <img src="../images/overview/browser-action-with-popup.png"
+    <img src="{{static}}/images/overview/browser-action-with-popup.png"
       width="147" height="100"
       alt="screenshot" />
   </td>
 </tr>
 
 <tr>
   <td>
     This <a href="samples.html#gmail">mail extension</a>
     uses a <em>browser action</em>
     (icon in the toolbar).
@@ skipping 28 matching lines @@
 
 <h3 id="packagedapp-ui">Packaged app UIs</h3>
 
 <p>
 A packaged app usually presents its main functionality using
 an HTML page that's bundled into the app.
 For example, the following packaged app
 displays a Flash file within an HTML page.
 </p>
 
-<img src="../images/overview/flash-app.png"
+<img src="{{static}}/images/overview/flash-app.png"
   width="372" height="300"
   alt="screenshot" />
 
 <p>
 For more information,
 see <a href="apps.html">Packaged Apps</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&mdash;for
   example, image files</li>
 </ul>
 
@@ skipping 127 matching lines @@
 a browser action (yellow icon)
 and a page action (blue icon).
 Both the browser action and the page action
 have background pages.
 This figure shows the browser action's background page,
 which is defined by <code>background.html</code>
 and has JavaScript code that controls
 the behavior of the browser action in both windows.
 </p>
 
-<img src="../images/overview/arch-1.gif"
+<img src="{{static}}/images/overview/arch-1.gif"
  width="232" height="168"
  alt="Two windows and a box representing a background page (background.html). One window has a yellow icon; the other has both a yellow icon and a blue icon. The yellow icons are connected to the background page." />
 
 <p>
 Although background pages can be useful,
 don't use one if you don't need it.
 Background pages are always open,
 so when a user installs many extensions that have background pages,
 Chrome's performance can suffer.
 </p>
@@ skipping 62 matching lines @@
 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.
 </p>
 
-<img src="../images/overview/arch-2.gif"
+<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.html">Browser Actions</a>,
 <a href="options.html">Options</a>,
 <a href="override.html">Override Pages</a>,
 and the <a href="#pageComm">Communication between pages</a> section
 for more details.
 </p>
@@ skipping 24 matching lines @@
 <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.
 </p>
 
-<img src="../images/overview/arch-3.gif"
+<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)." />
 
 <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.
 </p>
 
-<img src="../images/overview/arch-cs.gif"
+<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." />
 
-<!-- [PENDING: Add overview of message passing.] -->
+
 
 <p>
 For more information,
 see <a href="content_scripts.html">Content Scripts</a>.
 </p>
 
 
 <h2 id="apis"> Using the chrome.* APIs </h2>
 
 <p>
@@ skipping 125 matching lines @@
 </p>
 
 <p>
 <iframe title="YouTube video player" width="640" height="390" src="http://www.youtube.com/embed/bmxr75CV36A?rel=0" frameborder="0" allowfullscreen></iframe>
 </p>
 
 <h2 id="pageComm">Communication between pages </h2>
 
 <p>
 The HTML pages within an extension often need to communicate.
-<!-- [PENDING: For example, ...] -->
+
 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.html"><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.
 </p>
 
-<!-- [PENDING: Here's an example of communication between xyz and the background page.  (code example goes here)] -->
+
 
 
 <h2 id="incognito"> Saving data and incognito mode </h2>
 
 <p>
 Extensions can save data using
 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,
@@ skipping 55 matching lines @@
 
 <ul>
   <li> <a href="getstarted.html">Tutorial: Getting Started</a> </li>
   <li> <a href="tut_debugging.html">Tutorial: Debugging</a> </li>
   <li> <a href="devguide.html">Developer's Guide</a> </li>
   <li> <a href="http://dev.chromium.org/developers/design-documents/extensions/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>
-</ul>
+</ul>