[NaCl SDK Docs] Remove links to developers.google.com

native_client_sdk/src/doc/devguide/coding/3D-graphics.rst

 .. _devguide-coding-3D-graphics:
 
 ###########
 3D Graphics
 ###########
 
 Native Client applications use the `OpenGL ES 2.0
 <http://en.wikipedia.org/wiki/OpenGL_ES>`_ API for 3D rendering. This document
 describes how to call the OpenGL ES 2.0 interface in a Native Client module and
 how to build an efficient rendering loop. It also explains how to validate GPU
@@ skipping 101 matching lines @@
   ``glGetIntegerv(GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS, ...)`` and
   ``glGetIntegerv(GL_MAX_TEXTURE_SIZE, ...)`` return values greater than 0.
 
 * If you are using more than 8 textures in a single shader, make sure
   ``glGetIntegerv(GL_MAX_TEXTURE_IMAGE_UNITS, ...)`` returns a value greater
   than or equal to the number of simultaneous textures you need.
 
 Vetting the driver in the Chrome Web Store
 ------------------------------------------
 
-If you choose to place your application in the `Chrome Web
-Store <https://developers.google.com/chrome/web-store/docs/>`_, its Web Store
-`manifest file <http://code.google.com/chrome/extensions/manifest.html>`_ can
-include the ``webgl`` feature in the requirements parameter. It looks like this:
+If you choose to place your application in the `Chrome Web Store </webstore>`_,
+its Web Store `manifest file </extensions/manifest>`_ can include the ``webgl``
+feature in the requirements parameter. It looks like this:
 
 .. naclcode::
 
   "requirements": {
     "3D": {
       "features": ["webgl"]
     }
   }
 
 While WebGL is technically a JavaScript API, specifying the ``webgl`` feature
 also works for OpenGL ES 2.0 because both interfaces use the same driver.
 
 This manifest item is not required, but if you include it, the Chrome Web Store
 will prevent a user from installing the application if the browser is running on
 a machine that does not support OpenGL ES 2.0 or that is using a known
 blacklisted GPU driver that could invite an attack.
 
 If the Web Store determines that the user's driver is deficient, the app won't
 appear on the store's tile display. However, it will appear in store search
 results or if the user links to it directly, in which case the user could still
 download it. But the manifest requirements will be checked when the user reaches
 the install page, and if there is a problem, the browser will display the
 message "This application is not supported on this computer. Installation has
 been disabled."
 
 The manifest-based check applies only to downloads directly from the Chrome Web
 Store. It is not performed when an application is loaded via `inline
-installation
-<https://developers.google.com/chrome/web-store/docs/inline_installation>`_.
+installation </webstore/inline_installation>`_.
 
 What to do when there are problems
 ----------------------------------
 
 Using the vetting procedure described above, you should be able to detect the
 most common problems before your application runs. If there are problems, your
 code should describe the issue as clearly as possible. That's easy if there is a
 missing feature. Failure to create a graphics context is tougher to diagnose. At
 the very least, you can suggest that the user try to update the driver.  You
 might want to linke to the Chrome page that describes `how to do updates
@@ skipping 91 matching lines @@
 supports many versions of OpenGL. Regal recently added support for Native
 Client. Regal forwards most OpenGL calls directly to the underlying graphics
 library, but it can also emulate other calls that are not included (when
 hardware support exists). See `libregal
 <http://www.altdevblogaday.com/2012/09/04/bringing-regal-opengl-to-native-client/>`_
 for more info.
 
 Use the Pepper API
 ------------------
 
-Your code can call the Pepper `PPB_OpenGLES2
-<https://developers.google.com/native-client/pepperc/struct_p_p_b___open_g_l_e_s2>`_
-API directly, as with any Pepper interface. When you write in this way, each
-invocation of an OpenGL ES 2.0 function must begin with a reference to the
-Pepper interface, and the first argument is the graphics context. To invoke the
-function ``glCompileShader``, your code might look like:
+Your code can call the Pepper PPB_OpenGLES2 API directly, as with any Pepper
+interface. When you write in this way, each invocation of an OpenGL ES 2.0
+function must begin with a reference to the Pepper interface, and the first
+argument is the graphics context. To invoke the function ``glCompileShader``,
+your code might look like:
 
 .. naclcode::
 
   ppb_g3d_interface->CompileShader(graphicsContext, shader);
 
 This approach specifically targets the Pepper APIs. Each call corresponds to a
 OpenGL ES 2.0 function, but the syntax is unique to Native Client, so the source
 file is not portable.
 
 Implementing a rendering loop
@@ skipping 13 matching lines @@
 a new, separate sandboxed process. The module's process has its own main thread
 (the Native Client thread). The Chrome and Native Client processes communicate
 with each other using Pepper API calls on their main threads.
 
 When the Chrome main thread calls the Native Client thread (keyboard and mouse
 callbacks, for example), the Chrome main thread will block. This means that
 lengthy operations on the Native Client thread can steal cycles from Chrome, and
 performing blocking operations on the Native Client thread can bring your app to
 a standstill.
 
-Native Client uses callback functions to synchronize the main threads of the two
-processes. Only certain Pepper functions use callbacks; `SwapBuffers
-<https://developers.google.com/native-client/pepperc/struct_p_p_b___graphics3_d__1__0#a293c6941c0da084267ffba3954793497>`_
+Native Client uses callback functions to synchronize the main threads of the
+two processes. Only certain Pepper functions use callbacks; `SwapBuffers
+</native-client/pepper_stable/c/struct_p_p_b___graphics3_d__1__0#a293c6941c0da084267ffba3954793497>`_
 is one.
 
 ``SwapBuffers`` and its callback function
 -----------------------------------------
 
 ``SwapBuffers`` is non-blocking; it is called from the Native Client thread and
 returns immediately. When ``SwapBuffers`` is called, it runs asynchronously on
 the Chrome main thread. It switches the graphics data buffers, handles any
 needed compositing operations, and redraws the screen. When the screen update is
 complete, the callback function that was included as one of ``SwapBuffer``'s
@@ skipping 206 matching lines @@
 * **Don't read data from the GPU.** Don't call ``glReadPixels``, as it is slow.
 
 * **Don't update a small portion of a large buffer.** In the current OpenGL ES
   2.0 implementation when you update a portion of a buffer (with
   ``glSubBufferData`` for example) the entire buffer must be reprocessed. To
   avoid this problem, keep static and dynamic data in different buffers.
 
 * **Don't call ``glDisable(GL_TEXTURE_2D)``.** This is an OpenGL ES 2.0
   error. Each time it is called, an error messages will appear in Chrome's
   ``about:gpu`` tab.