diff options
author | jmedley <jmedley@chromium.org> | 2014-09-11 12:20:47 -0700 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2014-09-11 19:22:50 +0000 |
commit | 33f9e20d3cfe906de7fbdb25b204b68a6f1e4680 (patch) | |
tree | 7b9b6c2dab232f25b3c476c4802618bad4627d82 /native_client_sdk/doc_generated | |
parent | 637c06b0c0b9a445191c8a244484a561eda0f743 (diff) | |
download | chromium_src-33f9e20d3cfe906de7fbdb25b204b68a6f1e4680.zip chromium_src-33f9e20d3cfe906de7fbdb25b204b68a6f1e4680.tar.gz chromium_src-33f9e20d3cfe906de7fbdb25b204b68a6f1e4680.tar.bz2 |
Fix broken links on landing page.
BUG=none
R=
TEST=none
NOTRY=true
(documentation only change)
Review URL: https://codereview.chromium.org/549043004
Cr-Commit-Position: refs/heads/master@{#294441}
Diffstat (limited to 'native_client_sdk/doc_generated')
-rw-r--r-- | native_client_sdk/doc_generated/index.html | 48 |
1 files changed, 26 insertions, 22 deletions
diff --git a/native_client_sdk/doc_generated/index.html b/native_client_sdk/doc_generated/index.html index 38fb7c9..93881bc 100644 --- a/native_client_sdk/doc_generated/index.html +++ b/native_client_sdk/doc_generated/index.html @@ -18,8 +18,8 @@ Native Client, including its goals, how it works, and how Portable Native Client lets developers run native compiled code on the web.</p> <aside class="note"> This site uses several examples of Native Client. For the best experience, -consider downloading the <a class="reference external" href="http://www.google.com/chrome/">latest version of Chrome</a>. -When you come back, be sure to <a class="reference external" href="https://gonativeclient.appspot.com/demo">check out our demos</a>. +consider downloading the <a class="reference external" href="http://www.google.com/chrome/">latest version of Chrome</a>. When you come back, be sure to <a class="reference external" href="https://gonativeclient.appspot.com/demo">check out +our demos</a>. </aside> </div> @@ -28,43 +28,47 @@ src="//www.youtube.com/embed/MvKEomoiKBA?rel=0" frameborder="0"></iframe> <div class="big-intro"><h2 id="two-types-of-modules">Two Types of Modules</h2> <p>Native Client comes in two flavors.</p> <ul class="small-gap"> -<li><strong>Portable Native Client (PNaCl)</strong>: Pronounced ‘pinnacle’, PNaCl runs single, portable (<strong>pexe</strong>) executables and is available -in most implementations of Chrome. A translator built into Chrome -translates the pexe into native code for the client hardware. The entire -module is translated before any code is executed rather than as the code is -executed. PNaCl modules can be hosted from any web server.</li> +<li><strong>Portable Native Client (PNaCl)</strong>: Pronounced ‘pinnacle’, PNaCl runs single, +portable (<strong>pexe</strong>) executables and is available in most implementations of +Chrome. A translator built into Chrome translates the pexe into native code +for the client hardware. The entire module is translated before any code is +executed rather than as the code is executed. PNaCl modules can be hosted from +any web server.</li> <li><strong>Native Client (NaCl)</strong>: Also called traditional or non-portable Native -Client, NaCl runs -architecture-dependent (<strong>nexe</strong>) modules, which are packaged into an -application. At runtime, the browser decides which nexe to load based on the -architecture of the client machine. NaCl modules must be run from the <a class="reference external" href="https://chrome.google.com/webstore/category/apps">Chrome -Web Store (CWS)</a>. -Fortunately, work from PNaCl modules can be used to create NaCl modules.</li> +Client, NaCl runs architecture-dependent (<strong>nexe</strong>) modules, which are +packaged into an application. At runtime, the browser decides which nexe to +load based on the architecture of the client machine. NaCl modules must be run +from the <a class="reference external" href="https://chrome.google.com/webstore/category/apps">Chrome Web Store (CWS)</a>. Fortunately, work from +PNaCl modules can be used to create NaCl modules.</li> </ul> -<p>These flavors are described in more depth in <a class="reference external" href="nacl-and-pnacl">PNaCl and NaCl</a></p> +<p>These flavors are described in more depth in <a class="reference internal" href="/native-client/nacl-and-pnacl.html"><em>PNaCl and NaCl</em></a></p> <div class="left-side"> <div class="left-side-inner"> <h2>Hello World</h2> -<div class="big-intro"><p>To jump right in <a class="reference external" href="devguide/tutorial/tutorial-part1">take the tutorial</a> that walks you through a basic web -application for Portable Native Client (PNaCl). This is a client-side -application that uses HTML, JavaScript, and a Native Client module written in C++.</p> +<div class="big-intro"><p>To jump right in <a class="reference internal" href="/native-client/devguide/tutorial/tutorial-part1.html"><em>take the tutorial</em></a> +that walks you through a basic web application for Portable Native Client +(PNaCl). This is a client-side application that uses HTML, JavaScript, and a +Native Client module written in C++.</p> </div> </div> </div> <h2>A Little More Advanced</h2> -<div class="big-intro"><p>If you’ve already got the basics down, you’re probably trying to get a real application ready for production. You’re <a class="reference external" href="/devguide/devcycle/building">building</a>, <a class="reference external" href="/devguide/devcycle/debugging">debugging</a> or <a class="reference external" href="/devguide/distributing">ready to distribute</a>.</p> +<div class="big-intro"><p>If you’ve already got the basics down, you’re probably trying to get a real +application ready for production. You’re <a class="reference internal" href="/native-client/devguide/devcycle/building.html"><em>building</em></a>, <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html"><em>debugging</em></a> +or <a class="reference internal" href="/native-client/devguide/distributing.html"><em>ready to distribute</em></a>.</p> </div> <div class="left-side"> <div class="left-side-inner"> <h2>Nuts and Bolts</h2> -<div class="big-intro"><p>You’ve been working on a Native Client module for a while now and you’ve run into an arcane problem. You may need to refer to the <a class="reference external" href="/reference/pnacl-bitcode-abi">PNaCl Bitcode Reference</a> or the <a class="reference external" href="/sandbox_internals/index">Sandbox internals</a>.</p> +<div class="big-intro"><p>You’ve been working on a Native Client module for a while now and you’ve run +into an arcane problem. You may need to refer to the <a class="reference internal" href="/native-client/reference/pnacl-bitcode-abi.html"><em>PNaCl Bitcode +Reference</em></a> or the <a class="reference internal" href="/native-client/reference/sandbox_internals/index.html"><em>Sandbox internals</em></a>.</p> </div> </div> </div><h2 id="i-want-to-know-everything">I Want to Know Everything</h2> -<p>So, you like to read now and try later. Start with our <a class="reference external" href="/overview">Technical Overview</a></p> -<div class="big-intro" style="clear: both;"><p>Send us questions, comments, and feedback: -<a class="reference external" href="https://groups.google.com/forum/#!forum/native-client-discuss">native-client-discuss</a>.</p> +<p>So, you like to read now and try later. Start with our <a class="reference internal" href="/native-client/overview.html"><em>Technical Overview</em></a></p> +<div class="big-intro" style="clear: both;"><p>Send us questions, comments, and feedback: <a class="reference external" href="https://groups.google.com/forum/#!forum/native-client-discuss">native-client-discuss</a>.</p> </div></section> {{/partials.standard_nacl_article}} |