diff options
| author | jmedley <jmedley@chromium.org> | 2014-08-25 09:41:52 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2014-08-25 16:43:06 +0000 |
| commit | d8030556408b675d29fd0446a10eeba50b2a2c84 (patch) | |
| tree | 1d890fd13b813771b73e439d5b75566b43aab754 /native_client_sdk/doc_generated/devguide/coding/application-structure.html | |
| parent | 4963830383cd11d5ad000504a3f9dcc49ec122d4 (diff) | |
| download | chromium_src-d8030556408b675d29fd0446a10eeba50b2a2c84.zip chromium_src-d8030556408b675d29fd0446a10eeba50b2a2c84.tar.gz chromium_src-d8030556408b675d29fd0446a10eeba50b2a2c84.tar.bz2 | |
Per P0 reqs add launch points + make download obvious. Also misc copy edits.
BUG=none
R= mkearney@chromium.org, smain@chromium.org, binji@chromium.org
TEST=none
NOTRY=true
(documentation only change)
Priority list copied here for reference:
P1 But written by different engineers, very uneven quality and voice.
P2 Some documentation could be expanded.
P0 The ramp-in for new users could be improved.
P0 The landing page isn't "cool", it doesn't make developers want to jump in and use it.
Could we have a more github-like thing that gets people started quickly?
Could we have a narrative intro?
We just bought the pna.cl domain, we should use it!
P3 We think it's pretty important to keep the deep-dive in there (e.g. sandbox internals, bitcode reference).
Review URL: https://codereview.chromium.org/476793002
Cr-Commit-Position: refs/heads/master@{#291696}
Diffstat (limited to 'native_client_sdk/doc_generated/devguide/coding/application-structure.html')
| -rw-r--r-- | native_client_sdk/doc_generated/devguide/coding/application-structure.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/native_client_sdk/doc_generated/devguide/coding/application-structure.html b/native_client_sdk/doc_generated/devguide/coding/application-structure.html index 3391274..f53fd4e 100644 --- a/native_client_sdk/doc_generated/devguide/coding/application-structure.html +++ b/native_client_sdk/doc_generated/devguide/coding/application-structure.html @@ -11,8 +11,8 @@ <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 -Native Client application. The chapter assumes you are familiar with the +</div><p>This section of the Developer’s Guide describes the general structure of a +Native Client application. The section 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"> The “Hello, World” example is used here to illustrate basic @@ -204,7 +204,7 @@ issue a <code>crash</code> event <a class="reference internal" href="/native-client/devguide/coding/progress-events.html"><em>which can be handled in Javascript</em></a>.</p> <p>While the <code>CreateModule()</code> factory function, the <code>Module</code> class, and the <code>Instance</code> class are required for a Native Client application, the code -samples shown above don’t actually do anything. Subsequent chapters in the +samples shown above don’t actually do anything. Subsequent sections in the Developer’s Guide build on these code samples and add more interesting functionality.</p> </section> |