Move chrome.experimental.app.onLaunched event handler to chrome.app.runtime.onLaunched.

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

 <h1>Connect Apps with Web Intents</h1>
 
 
 <p>
 <a href="http://webintents.org/">Web Intents</a>
 allow your application to quickly communicate
 with other applications on the user's system and inside their browser.
 Your application can register to handle specific user actions
 such as editing images via the <code>manifest.json</code>;
 your application can also invoke actions to be handled by other applications.
@@ skipping 48 matching lines @@
    "title" : "RSS Feed Reader",
    "type" : ["application/atom+xml", "application/rss+xml"]
  }]
 }
 </pre>
 
 <p>
 Your application will receive intent payload through the <code>onLaunched</code> event.
 </p>
 <pre>
-chrome.experimental.app.onLaunched(function(intent) {
+chrome.app.runtime.onLaunched(function(intent) {
   // App Launched
   if(intent.action == "http://webinents.org/view" &amp;&amp;
      intent.type == "application/atom+xml") {
 
     // obtain the ATOM feed data.
     var data = intent.data;
   }
 });
 </pre>
 
 
 <h2 id="launching">Launching an app with a file</h2>
 <p>
 If your app handles the <code>view</code> intent,
 it is possible to launch it from the command line with a file as a parameter.
 </p>
 <pre>
 chrome.exe --app-id [app_id] [path_to_file]
 </pre>
 <p>
 This will implicity launch your application with an intent payload populated
 with the action set to "http://webintents.org/view", the type set to the 
 mime-type of the file and the data as a <code>FileEntry</code> object.
 </p>
 <pre>
-chrome.experimental.app.onLaunched(function(intent) {
+chrome.app.runtime.onLaunched(function(intent) {
   // App Launched
   var data = intent.data;
 });
 </pre>
 
 <h2 id="launching">Manipulating the file</h2>
 <p>
   When your application is launched with a file as the parameter
   on the command-line,
   the <code>intent.data</code> property is a <code>FileEntry</code>.
   This is really cool because now you have a direct reference back to the physical
   file on the disk,
   and you can write data back to it.
 </p>
 
 <pre>
-chrome.experimental.app.onLaunched(function(intent) {
+chrome.app.runtime.onLaunched(function(intent) {
   // App Launched
   var data = intent.data;
   if(data instanceof FileEntry) {
     data.createWriter(function(writer) {
       writer.onwriteend = function(e) {
         console.log('Write completed.');
       };
 
       writer.onerror = function(e) {
         console.log('Write failed: ' + e.toString());
@@ skipping 10 matching lines @@
 
 <h2 id="return">Returning data to calling application</h2>
 <p>
 Lots of applications want to cooperate
 with the app that invoked them.
 It's easy to send data back to the calling client
 using <code>intent.postResult</code>:
 </p>
 
 <pre>
-chrome.experimental.app.onLaunched(function(intent) {
+chrome.app.runtime.onLaunched(function(intent) {
   // App Launched
   console.log(intent.action);
   console.log(intent.type);
   var data = intent.data;
   // Do something with the data;
 
   intent.postResult(newData);
 });
 </pre>
 
@@ skipping 50 matching lines @@
 var intent = new WebKitIntent("http://webintents.org/edit", "image/png", "dataUri://");
 
 var onSuccess = function(data) {};
 var onError = function() {};
 
 window.navigator.webkitStartActivity(intent, onSuccess, onError);
 </pre>
 
 <h3>Service</h3>
 <pre>
-chrome.experimental.app.onLaunched(function(intent) {
+chrome.app.runtime.onLaunched(function(intent) {
   // App Launched
   console.log(intent.action);
   console.log(intent.type);
   var data = intent.data;
   // Do something with the data;
 
   intent.postResult(newData);
 });
 </pre>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>