Linking AvailabilityFinder with APIDataSource and intro-table templates.

chrome/common/extensions/docs/templates/private/intro_table.html

Index: chrome/common/extensions/docs/templates/private/intro_table.html
diff --git a/chrome/common/extensions/docs/templates/private/intro_table.html b/chrome/common/extensions/docs/templates/private/intro_table.html
new file mode 100644
index 0000000000000000000000000000000000000000..2703aa54a69c60887e789c35c547e089ef193f55
--- /dev/null
+++ b/chrome/common/extensions/docs/templates/private/intro_table.html
@@ -0,0 +1,65 @@
+<table class="intro">
+  <tr>
+    <th scope="col"></th>
+    <th scope="col"></th>
+  </tr>

[not at google - send to devlin, 2013/07/03 19:54:56]

what is this empty row for..?

[epeterson, 2013/07/09 20:51:18]

It was in the hardcoded intro tables, so I kind of just rolled with it.

But it looks like that scope attribute does nothing for browsers but is used for
screen readers?
I'm just going to get rid of it for now..

+  <tr>
+    <td>
+      <strong>Description:</strong>
+    </td>
+    <td>
+      {{?api.description}}
+        {{{api.description}}}
+      {{:}}
+        The <code>chrome.{{api.name}}</code> API

[not at google - send to devlin, 2013/07/03 19:54:56]

end in fullstop

[epeterson, 2013/07/09 20:51:18]

Done.

+      {{/api.description}}
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <strong>Availability:</strong>
+    </td>
+    <td>
+      {{?api.availability}}
+        Chrome {{api.availability}}
+      {{:api.availability}}
+        {{?api.experimental}}
+          Experimental only (see <a href="experimental.html#using">How to use experimental APIs</a>)
+        {{:api.experimental}}
+          Available.
+        {{/api.experimental}}

[not at google - send to devlin, 2013/07/03 19:54:56]

We need a richer data model here. Probably from API data source we'll set
- is_experimental
- is_dev
- is_beta
- stable_version

(only one of those).

There are already templates that exist for showing the dev/beta warnings, maybe
the experimental one, and then you'll need to add the "stable since Chrome X"
thing in here.

[epeterson, 2013/07/09 20:51:18]

This comment may have been outdated by your most recent request to change the
data model.

+      {{/api.availability}}
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <strong>Permissions:</strong>
+    </td>
+    <td>
+      {{?api.api_permissions}}
+        {{#api.api_permissions}}
+          {{?permission}}<code>{{permission}}</code>{{/permission}}
+          {{?extra}}{{{extra}}}{{/extra}}
+          <br>

[not at google - send to devlin, 2013/07/03 19:54:56]

why the <br>?

[epeterson, 2013/07/09 20:51:18]

There's the possibility of permissions line-wrapping, like here:
  http://developer.chrome.com/trunk/apps/mediaGalleries.html

<br>'s prevent this, at the expense of shorter permissions not being able to fit
all on one line, I suppose.
Doesn't having each permission on a separate line more accurately model how
permissions look when declared in a manifest, as well?

Of course, if permissions should look like they do in manifest files, then they
need double-quotes (which is what they have in the hardcoded tables)...so I
added those just now.

[not at google - send to devlin, 2013/07/09 23:11:55]

sgtm

+        {{/api.api_permissions}}
+      {{:api.api_permissions}}
+        None
+      {{/api.api_permissions}}
+    </td>
+  </tr>
+  {{?api.learn_more}}
+  <tr>
+    <td>
+      <strong>Learn more:</strong>
+    </td>
+    <td>
+      {{#api.learn_more}}
+        {{?prefix}}{{prefix}}{{/prefix}}
+        <a href='{{href}}'>{{content}}</a>
+        {{?suffix}}{{suffix}}{{/suffix}}
+        <br>
+      {{/api.learn_more}}
+    </td>
+  </tr>
+  {{/}}
+</table>