[NaCl SDK Docs] Remove table-of-contents from generated pages.
We don't want the TOC at the top of the chromesite pages, but we do for the devsite pages. The table-of-contents is in the .rst file, but we don't want to remove it in case we need to generate devsite documentation again. The easy hack for now is to set the style of the element to "display: none". Also, remove doc_generated/.buildinfo. This file should not be checked in. BUG=none R=sbc@chromium.org Review URL: https://codereview.chromium.org/146203002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@246928 0039d316-1c4b-4281-b951-d872f2087c98
This commit is contained in:
binji@chromium.org
native_client_sdk
doc_generated
.buildinfo.gitignorefaq.htmlnacl-and-pnacl.htmloverview.html
community
security-contest
devguide
coding
application-structure.htmlaudio.htmlfile-io.htmlmessage-system.htmlnacl_io.htmlnative-client-modules.htmlprogress-events.htmlurl-loading.htmlview-focus-input-events.html
devcycle
distributing.htmltutorial
reference
rest-devsite-examples.htmlsrc
doc
_sphinxext
@@ -2,7 +2,7 @@
|
||||
|
||||
<section id="application-structure">
|
||||
<span id="devcycle-application-structure"></span><h1 id="application-structure"><span id="devcycle-application-structure"></span>Application Structure</h1>
|
||||
<div class="contents local topic" id="contents">
|
||||
<div class="contents local" id="contents" style="display: none">
|
||||
<ul class="small-gap">
|
||||
<li><a class="reference internal" href="#application-components" id="id1">Application components</a></li>
|
||||
<li><a class="reference internal" href="#html-file-and-the-embed-element" id="id2">HTML file and the <embed> element</a></li>
|
||||
@@ -10,8 +10,8 @@
|
||||
<li><a class="reference internal" href="#modules-and-instances" id="id4">Modules and instances</a></li>
|
||||
<li><a class="reference internal" href="#native-client-modules-a-closer-look" id="id5">Native Client modules: A closer look</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<p>This chapter of the Developer’s Guide describes the general structure of a
|
||||
|
||||
</div><p>This chapter of the Developer’s Guide describes the general structure of a
|
||||
Native Client application. The chapter assumes you are familiar with the
|
||||
material presented in the <a class="reference internal" href="/native-client/overview.html"><em>Technical Overview</em></a>.</p>
|
||||
<aside class="note">
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
<section id="audio">
|
||||
<span id="devguide-coding-audio"></span><h1 id="audio"><span id="devguide-coding-audio"></span>Audio</h1>
|
||||
<div class="contents local topic" id="contents">
|
||||
<div class="contents local" id="contents" style="display: none">
|
||||
<ul class="small-gap">
|
||||
<li><a class="reference internal" href="#reference-information" id="id1">Reference information</a></li>
|
||||
<li><a class="reference internal" href="#about-the-pepper-audio-api" id="id2">About the Pepper audio API</a></li>
|
||||
@@ -23,8 +23,8 @@
|
||||
</li>
|
||||
<li><a class="reference internal" href="#starting-and-stopping-playback" id="id12">Starting and stopping playback</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<p>This chapter describes how to use the Pepper audio API to play an audio
|
||||
|
||||
</div><p>This chapter describes how to use the Pepper audio API to play an audio
|
||||
stream. The Pepper audio API provides a low-level means of playing a stream of
|
||||
audio samples generated by a Native Client module. The API generally works as
|
||||
follows: A Native Client module creates an audio resource that represents an
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
<section id="file-i-o">
|
||||
<span id="devguide-coding-fileio"></span><h1 id="file-i-o"><span id="devguide-coding-fileio"></span>File I/O</h1>
|
||||
<div class="contents local topic" id="contents">
|
||||
<div class="contents local" id="contents" style="display: none">
|
||||
<ul class="small-gap">
|
||||
<li><a class="reference internal" href="#introduction" id="id2">Introduction</a></li>
|
||||
<li><a class="reference internal" href="#reference-information" id="id3">Reference information</a></li>
|
||||
@@ -34,8 +34,8 @@
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<section id="introduction">
|
||||
|
||||
</div><section id="introduction">
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
<p>This chapter describes how to use the <a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_file_i_o">FileIO API</a>
|
||||
to read and write files using a local secure data store.</p>
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
<section id="messaging-system">
|
||||
<span id="message-system"></span><h1 id="messaging-system"><span id="message-system"></span>Messaging System</h1>
|
||||
<div class="contents local topic" id="contents">
|
||||
<div class="contents local" id="contents" style="display: none">
|
||||
<ul class="small-gap">
|
||||
<li><a class="reference internal" href="#reference-information" id="id2">Reference information</a></li>
|
||||
<li><p class="first"><a class="reference internal" href="#introduction-to-the-messaging-system" id="id3">Introduction to the messaging system</a></p>
|
||||
@@ -30,8 +30,8 @@
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<p>This chapter describes the messaging system used to communicate between the
|
||||
|
||||
</div><p>This chapter describes the messaging system used to communicate between the
|
||||
JavaScript code and the Native Client module’s C or C++ code in a
|
||||
Native Client application. It introduces the concept of asynchronous
|
||||
programming and the basic steps required to set up a Native Client module
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
<section id="the-nacl-io-library">
|
||||
<span id="nacl-io"></span><h1 id="the-nacl-io-library"><span id="nacl-io"></span>The nacl_io Library</h1>
|
||||
<div class="contents local topic" id="contents">
|
||||
<div class="contents local" id="contents" style="display: none">
|
||||
<ul class="small-gap">
|
||||
<li><a class="reference internal" href="#introduction" id="id1">Introduction</a></li>
|
||||
<li><a class="reference internal" href="#using-nacl-io" id="id2">Using nacl_io</a></li>
|
||||
@@ -14,8 +14,8 @@
|
||||
</li>
|
||||
<li><a class="reference internal" href="#reference-information" id="id6">Reference information</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<section id="introduction">
|
||||
|
||||
</div><section id="introduction">
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
<p><code>nacl_io</code> is a utility library that provides implementations of standard
|
||||
C APIs such as POSIX I/O (<code>stdio.h</code>) and BSD sockets (<code>sys/socket.h</code>).
|
||||
|
||||
@@ -6,14 +6,14 @@
|
||||
a Native Client module in order for Chrome to load, initialize, and run it. The
|
||||
requirements are the same regardless of whether or not the module uses PNaCl,
|
||||
but depend on whether the module is written in C or C++.</p>
|
||||
<div class="contents local topic" id="contents">
|
||||
<div class="contents local" id="contents" style="display: none">
|
||||
<ul class="small-gap">
|
||||
<li><a class="reference internal" href="#introduction" id="id2">Introduction</a></li>
|
||||
<li><a class="reference internal" href="#writing-modules-in-c" id="id3">Writing modules in C</a></li>
|
||||
<li><a class="reference internal" href="#id1" id="id4">Writing modules in C++</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<section id="introduction">
|
||||
|
||||
</div><section id="introduction">
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
<p>Native Client modules do not have a <code>main()</code> function. When a module loads,
|
||||
the Native Client runtime calls the code in the module to create an instance and
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
<section id="progress-events">
|
||||
<span id="devcycle-progress-events"></span><h1 id="progress-events"><span id="devcycle-progress-events"></span>Progress Events</h1>
|
||||
<div class="contents local topic" id="contents">
|
||||
<div class="contents local" id="contents" style="display: none">
|
||||
<ul class="small-gap">
|
||||
<li><a class="reference internal" href="#module-loading-and-progress-events" id="id3">Module loading and progress events</a></li>
|
||||
<li><a class="reference internal" href="#handling-progress-events" id="id4">Handling progress events</a></li>
|
||||
@@ -11,8 +11,8 @@
|
||||
<li><a class="reference internal" href="#the-readystate-attribute" id="id7">The <code>readyState</code> attribute</a></li>
|
||||
<li><a class="reference internal" href="#the-exitstatus-attribute" id="id8">The <code>exitStatus</code> attribute</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<p>There are five types of events that developers can respond to in Native Client:
|
||||
|
||||
</div><p>There are five types of events that developers can respond to in Native Client:
|
||||
progress, message, view change, focus, and input events (each described in the
|
||||
glossary below). This chapter describes how to monitor progress events (events
|
||||
that occur during the loading and execution of a Native Client module). This
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
<section id="url-loading">
|
||||
<span id="devguide-coding-url-loading"></span><h1 id="url-loading"><span id="devguide-coding-url-loading"></span>URL Loading</h1>
|
||||
<div class="contents local topic" id="contents">
|
||||
<div class="contents local" id="contents" style="display: none">
|
||||
<ul class="small-gap">
|
||||
<li><a class="reference internal" href="#introduction" id="id1">Introduction</a></li>
|
||||
<li><a class="reference internal" href="#reference-information" id="id2">Reference information</a></li>
|
||||
@@ -20,8 +20,8 @@
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<section id="introduction">
|
||||
|
||||
</div><section id="introduction">
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
<p>This chapter describes how to use the <a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_u_r_l_loader">URLLoader API</a>
|
||||
to load resources such as images and sound files from a server into your
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
<section id="view-change-focus-and-input-events">
|
||||
<span id="view-focus-input-events"></span><h1 id="view-change-focus-and-input-events"><span id="view-focus-input-events"></span>View Change, Focus, and Input Events</h1>
|
||||
<div class="contents local topic" id="contents">
|
||||
<div class="contents local" id="contents" style="display: none">
|
||||
<ul class="small-gap">
|
||||
<li><a class="reference internal" href="#overview" id="id2">Overview</a></li>
|
||||
<li><p class="first"><a class="reference internal" href="#handling-browser-events" id="id3">Handling browser events</a></p>
|
||||
@@ -19,8 +19,8 @@
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<p>This chapter describes view change, focus, and input event handling for a
|
||||
|
||||
</div><p>This chapter describes view change, focus, and input event handling for a
|
||||
Native Client module. The chapter assumes you are familiar with the
|
||||
material presented in the <a class="reference internal" href="/native-client/overview.html"><em>Technical Overview</em></a>.</p>
|
||||
<p>There are two examples used in this chapter to illustrate basic
|
||||
|
||||
Reference in New Issue
Block a user