Added deprecation notice for web intents.

Also added public template for app_intents.html doc back in so that previous bookmarks do not result in a 404.

Note that I've repeated the deprecation warning under each <h2> in case a developer winds up in a section via search. Eventually we will want to add an 'Instead, use...' sentence/paragraph once this is defined and at the same time
remove the bulk of content in place.

BUG=174262

Review URL: https://codereview.chromium.org/12211131

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@182058 0039d316-1c4b-4281-b951-d872f2087c98

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

 <h1>Connect Apps with Web Intents</h1>
 
+<p class="warning">
+<b>Warning: </b>
+Deprecated in Chrome 24.
+Web intents are no longer supported.
+</p>
 
 <p>
 <a href="http://webintents.org/">Web Intents</a>
@@ -22,6 +27,12 @@ Check out the
 
 <h2 id="register">Register your app to handle an action</h2>
 
+<p class="warning">
+<b>Warning: </b>
+Deprecated in Chrome 24.
+Web intents are no longer supported.
+</p>
+
 <p>
 You must supply the intent in the manifest:
 </p>
@@ -44,6 +55,12 @@ launch - the <code>onLaunched</code> event.
 
 <h2 id="content">Handling content types</h2>
 
+<p class="warning">
+<b>Warning: </b>
+Deprecated in Chrome 24.
+Web intents are no longer supported.
+</p>
+
 <p>
 Your application can be the user's preferred choice for handling a file type.
 For example, your application could handle viewing images or viewing pdfs.
@@ -77,8 +94,14 @@ chrome.app.runtime.onLaunched(function(intent) {
 });
 </pre>
 
-
 <h2 id="launching">Launching an app with a file</h2>
+
+<p class="warning">
+<b>Warning: </b>
+Deprecated in Chrome 24.
+Web intents are no longer supported.
+</p>
+
 <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.
@@ -99,6 +122,13 @@ chrome.app.runtime.onLaunched(function(intent) {
 </pre>
 
 <h2 id="launching">Manipulating the file</h2>
+
+<p class="warning">
+<b>Warning: </b>
+Deprecated in Chrome 24.
+Web intents are no longer supported.
+</p>
+
 <p>
   When your application is launched with a file as the parameter
   on the command-line,
@@ -131,6 +161,13 @@ chrome.app.runtime.onLaunched(function(intent) {
 </pre>
 
 <h2 id="return">Returning data to calling application</h2>
+
+<p class="warning">
+<b>Warning: </b>
+Deprecated in Chrome 24.
+Web intents are no longer supported.
+</p>
+
 <p>
 Lots of applications want to cooperate
 with the app that invoked them.
@@ -152,6 +189,12 @@ chrome.app.runtime.onLaunched(function(intent) {
 
 <h2 id="localize">Localizing your app title</h2>
 
+<p class="warning">
+<b>Warning: </b>
+Deprecated in Chrome 24.
+Web intents are no longer supported.
+</p>
+
 <p>
 If your application or extension is localized
 as per the guidelines in
@@ -171,6 +214,13 @@ using the exact same infrastructure:
 </pre>
 
 <h2 id="invoke">Invoking an action</h2>
+
+<p class="warning">
+<b>Warning: </b>
+Deprecated in Chrome 24.
+Web intents are no longer supported.
+</p>
+
 <p>
 If your application needs to be able
 to use the functionality of another application,
@@ -188,6 +238,13 @@ window.navigator.webkitStartActivity(intent, function(data) {
 </pre>
 
 <h2 id="errors">Handling Errors and Exceptions</h2>
+
+<p class="warning">
+<b>Warning: </b>
+Deprecated in Chrome 24.
+Web intents are no longer supported.
+</p>
+
 <p>
    If your service application needs to signal to the client application
    that an unrecoverable error has occurred,

chrome/common/extensions/docs/templates/public/apps/app_intents.html

+{{+partials.standard_apps_article article:intros.app_intents}}