Extensions Docs Server: Doc conversion script - SVN

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

 <meta name="doc-family" content="apps">
-<div id="pageData-name" class="pageData">Manage App Lifecycle</div>
-<div id="pageData-showTOC" class="pageData">true</div>
+<h1>Manage App Lifecycle</h1>
+
 
 <p>
 The app runtime and event page are responsible
 for managing the app lifecycle.
 The app runtime manages app installation,
 controls the event page,
 and can shutdown the app at anytime.
 The event page listens out for events from the app runtime
 and manages what gets launched and how.
 </p>
 
 <h2 id="lifecycle">How the lifecycle works</h2>
 
 <p>
 The app runtime loads the event page
 from a user's desktop and
 the <code>onLaunch()</code> event is fired.
 This event tells the event page what windows
 to launch and their dimensions.
 The lifecycle diagram here isn't the nicest to look at,
 but it's practical (and we will make it nicer soon).
 </p>
 
-<img src="../images/applifecycle.png"
+<img src="{{static}}/images/applifecycle.png"
      width="444"
      height="329"
      alt="how app lifecycle works">
 
 <p>
 When the event page has no executing JavaScript,
 no pending callbacks, and no open windows,
 the runtime unloads the event page and closes the app.
 Before unloading the event page,
 the <code>onSuspend()</code> event is fired.
@@ skipping 182 matching lines @@
 while handling this event are not guaranteed to complete.
 Keep the clean-up tasks synchronous and simple.
 </p>
 
 <pre>
 chrome.runtime.onSuspend.addListener(function() { 
   // Do some simple clean-up tasks.
 });
 </pre>
 
-<p class="backtotop"><a href="#top">Back to top</a></p>
+<p class="backtotop"><a href="#top">Back to top</a></p>