Adding two codelabs for cds2014.

native_client_sdk/src/doc/io2014.rst

Index: native_client_sdk/src/doc/io2014.rst
diff --git a/native_client_sdk/src/doc/io2014.rst b/native_client_sdk/src/doc/io2014.rst
index d61c50bd2b1b9e80af01cd1d3941716103ad8d31..68a6ef047fc669f46c0d8a5dc2e52218ede310c4 100644
--- a/native_client_sdk/src/doc/io2014.rst
+++ b/native_client_sdk/src/doc/io2014.rst
@@ -19,24 +19,7 @@ Work either on-line or off-line!
   <iframe class="video" width="500" height="281"
   src="//www.youtube.com/embed/OzNuzBDEWzk?rel=0" frameborder="0"></iframe>
 
-Work in Progress
-================
-
-These development tools are a work in progress, see `Feature Status`_.
-At this point, they are a learning tool and demonstration of NaCl's
-flexibility, but are not the recommended tools for a production application.
-To develop a substantial application for Native Client /
-Portable Native Client,
-we currently recommend you use the
-`Native Client SDK </native-client/sdk/download>`_.
-
-.. raw:: html
-
-  <b><font color="#880000">
-  NOTE: The NaCl Development Environment is not yet stable.
-  Ideally user data is preserved, but currently it can be lost during updates
-  or sporadically. We're working to resolve this.
-  </font></b>
+.. include:: nacldev/web_tools_note.inc
 
 Installation
 ============
@@ -74,48 +57,11 @@ Once you're ready to apply the debugger, follow these steps:
   * NOTE: If you experience unexplained hangs, disable GDB-based debugging
     temporarily and try again.
 
-Editor
-======
-
-To follow along in this tutorial, you'll need to use a text editor to modify
-various files in our development environment.
-There are currently two editor options, nano or vim.
-Emacs is coming soon...
-If you're unsure what to pick, nano is simpler to start with and has on-screen
-help.
-
-* You can open **nano** like this::
-
-    $ nano <filename>
-
-  Here's an online `nano tutorial <http://mintaka.sdsu.edu/reu/nano.html>`_.
-
-* You can open **vim** like this::
-
-    $ vim <filename>
-
-  Here's an online `vim tutorial <http://www.openvim.com/tutorial.html>`_.
-
-
-Git Setup
-=========
-
-This tutorial also uses a revision control program called
-`git <http://en.wikipedia.org/wiki/Git_(software)>`_.
-In order to commit to a git repository,
-you need to setup your environment to with your identity.
 
-You'll need to add these lines to `~/.bashrc` to cause them to be invoked each
-time you start the development environment.
-::
+.. include:: nacldev/editing.inc
 
-  git config --global user.name "John Doe"
-  git config --global user.email johndoe@example.com
+.. include:: nacldev/git.inc
 
-You can reload you `~/.bashrc` by running:
-::
-
-  source ~/.bashrc
 
 Tour (follow the video)
 =======================
@@ -257,44 +203,4 @@ Thanks for checking out our environment.
 Things are rapidly changing and in the coming months you can expect to see
 further improvements and filling out of our platform and library support.
 
-Check back at this page for the latest status.
-
-Feature Status
-==============
-
-Here is a summary of feature status. We hope to overcome these limitations
-in the near future:
-
-  * NaCl Development Environment
-
-    * General
-
-      * Supported:
-
-        * Python (built-in)
-        * GCC w/ GLibC (x86-32 and x86-64 only)
-        * Lua (install with: `package -i lua && . setup-environment`)
-        * Ruby (install with: `package -i ruby && . setup-environment`)
-        * Nethack! (install with: `package -i nethack && . setup-environment`)
-
-      * Unsupported:
-
-        * Targeting Newlib
-        * Targeting PNaCl
-        * Forking in bash
-        * Pipes / Redirection
-        * Symbolic and hard links
-
-    * Missing / broken on ARM:
-
-      * Git (broken)
-      * GCC (unsupported)
-
-  * Debugger
- 
-    * Runs reliably only on a recent Beta or Dev Channel (M36+) build.
-    * Currently unreliable on some platforms:
-      
-      * ChromeOS
-      * Mac OSX
-      * Windows
+Follow the status of the NaCl Dev Environment at `this page <naclenv>`_.