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

native_client_sdk/src/doc/devguide/coding/view-focus-input-events.rst

 .. _view_focus_input_events:
 
 ####################################
 View Change, Focus, and Input Events
 ####################################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
@@ skipping 11 matching lines @@
 directories in the Native Client SDK.  There is also the
 ppapi_simple library that can be used to to implement most of the
 boiler plate.  The ``pi_generator`` example in
 ``/examples/demo/pi_generator`` uses ppapi_simple to manage view
 change events and 2D graphics.
 
 
 Overview
 ========
 
-When a user interacts with the web page using a keyboard, mouse or
-some other input device, the browser generates input events.
-In a traditional web application, these input events are
-passed to and handled in JavaScript, typically through event listeners
-and event handlers. In a Native Client application, user interaction
-with an instance of a module (e.g., clicking inside the rectangle
-managed by a module) also generates input events, which are passed to
-the module. The browser also passes view change and focus events that
-affect a module's instance to the module. Native Client modules can
+When a user interacts with the web page using a keyboard, mouse or some other
+input device, the browser generates input events.  In a traditional web
+application, these input events are passed to and handled in JavaScript,
+typically through event listeners and event handlers. In a Native Client
+application, user interaction with an instance of a module (e.g., clicking
+inside the rectangle managed by a module) also generates input events, which
+are passed to the module. The browser also passes view change and focus events
+that affect a module's instance to the module. Native Client modules can
 override certain functions in the `pp::Instance
-<https://developers.google.com/native-client/peppercpp/classpp_1_1_instance>`_
-class to handle input and browser events. These functions are listed in
-the table below:
+</native-client/pepper_stable/cpp/classpp_1_1_instance>`_ class to handle input
+and browser events. These functions are listed in the table below:
 
 
 ======================  ===============================  ====================
 Function                  Event                            Use
 ======================  ===============================  ====================
 ``DidChangeView``       Called when the position,        An implementation
                         size, or clip rectangle          of this function
                         of the module's instance in      might check the size
                         the browser has changed.         of the module
                         This event also occurs           instance's rectangle
@@ skipping 49 matching lines @@
                         ``RequestInputEvents()``
                         for mouse events and
                         ``RequestFilteringInputEvents``
                         for keyboard events
                         prior to overriding this
                         function.
 ======================  ===============================  ====================
 
 
 These interfaces are found in the `pp::Instance class
-<https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_instance>`_.
-The sections below provide examples of how to handle these events.
+</native-client/pepper_stable/cpp/classpp_1_1_instance>`_.  The sections below
+provide examples of how to handle these events.
 
 
 Handling browser events
 =======================
 
 DidChangeView()
 ---------------
 
 In the ``mouse_lock`` example, ``DidChangeView()`` checks the previous size
 of instance's rectangle versus the new size.  It also compares
@@ skipping 23 matching lines @@
     // ...
 
     // Remember if we are fullscreen or not
     was_fullscreen_ = view.IsFullscreen();
     // ...
   }
 
 
 For more information about graphics contexts and how to manipulate images, see:
 
-* `pp::ImageData class <https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_image_data>`_
-* `pp::Graphics2D class <https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_graphics2_d>`_
+* `pp::ImageData class
+  </native-client/pepper_stable/cpp/classpp_1_1_image_data>`_
+* `pp::Graphics2D class
+  </native-client/pepper_stable/cpp/classpp_1_1_graphics2_d>`_
 
 
 DidChangeFocus()
 ----------------
 
 ``DidChangeFocus()`` is called when you click inside or outside of a
 module's instance in the web page. When the instance goes out
 of focus (click outside of the instance), you might do something
 like stop an animation. When the instance regains focus, you can
 restart the animation.
@@ skipping 32 matching lines @@
         : pp::Instance(instance), event_thread_(NULL), callback_factory_(this) {
       RequestInputEvents(PP_INPUTEVENT_CLASS_MOUSE | PP_INPUTEVENT_CLASS_WHEEL |
                          PP_INPUTEVENT_CLASS_TOUCH);
       RequestFilteringInputEvents(PP_INPUTEVENT_CLASS_KEYBOARD);
     }
     // ...
   };
 
 
 ``RequestInputEvents()`` and ``RequestFilteringInputEvents()`` accept a
-combination of flags that identify the class of events that the
-instance is requesting to receive. Input event classes are defined in
-the `PP_InputEvent_Class
-<https://developers.google.com/native-client/dev/pepperc/group___enums.html#gafe68e3c1031daa4a6496845ff47649cd>`_
+combination of flags that identify the class of events that the instance is
+requesting to receive. Input event classes are defined in the
+`PP_InputEvent_Class
+</native-client/pepper_stable/c/group___enums.html#gafe68e3c1031daa4a6496845ff47649cd>`_
 enumeration in `ppb_input_event.h
-<https://developers.google.com/native-client/dev/pepperc/ppb__input__event_8h>`_.
+</native-client/pepper_stable/c/ppb__input__event_8h>`_.
 
 
 Determining and branching on event types
 ----------------------------------------
 
-In a typical implementation, the ``HandleInputEvent()`` function
-determines the type of each event using the ``GetType()`` function found
-in the ``InputEvent`` class. The ``HandleInputEvent()`` function then uses a
-switch statement to branch on the type of input event. Input events
-are defined in the `PP_InputEvent_Type
-<https://developers.google.com/native-client/dev/pepperc/group___enums.html#gaca7296cfec99fcb6646b7144d1d6a0c5>`_
+In a typical implementation, the ``HandleInputEvent()`` function determines the
+type of each event using the ``GetType()`` function found in the ``InputEvent``
+class. The ``HandleInputEvent()`` function then uses a switch statement to
+branch on the type of input event. Input events are defined in the
+`PP_InputEvent_Type
+</native-client/pepper_stable/c/group___enums.html#gaca7296cfec99fcb6646b7144d1d6a0c5>`_
 enumeration in `ppb_input_event.h
-<https://developers.google.com/native-client/dev/pepperc/ppb__input__event_8h>`_.
+</native-client/pepper_stable/c/ppb__input__event_8h>`_.
 
 .. naclcode::
 
   virtual bool HandleInputEvent(const pp::InputEvent& event) {
     Event* event_ptr = NULL;
     switch (event.GetType()) {
       case PP_INPUTEVENT_TYPE_UNDEFINED:
         break;
       case PP_INPUTEVENT_TYPE_MOUSEDOWN:
       case PP_INPUTEVENT_TYPE_MOUSEUP:
@@ skipping 60 matching lines @@
     return true;
   }
 
 
 Notice that the generic ``InputEvent`` received by ``HandleInputEvent()`` is
 converted into a specific type after the event type is
 determined.  The event types handled in the example code are
 ``MouseInputEvent``, ``WheelInputEvent``, and ``KeyboardInputEvent``.
 There are also ``TouchInputEvents``.  For the latest list of event types,
 see the `InputEvent documentation
-<https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_input_event>`_.
+</native-client/pepper_stable/c/classpp_1_1_input_event>`_.
 For reference information related to the these event classes, see the
 following documentation:
 
-* `pp::MouseInputEvent class <https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_mouse_input_event>`_
-* `pp::WheelInputEvent class <https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_wheel_input_event>`_
-* `pp::KeyboardInputEvent class <https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_keyboard_input_event>`_
+* `pp::MouseInputEvent class
+  </native-client/pepper_stable/c/classpp_1_1_mouse_input_event>`_
+* `pp::WheelInputEvent class
+  </native-client/pepper_stable/c/classpp_1_1_wheel_input_event>`_
+* `pp::KeyboardInputEvent class
+  </native-client/pepper_stable/c/classpp_1_1_keyboard_input_event>`_
 
 
 Threading and blocking
 ----------------------
 
 ``HandleInputEvent()`` in this example runs on the main module thread.
 However, the bulk of the work happens on a separate worker thread (see
 ``ProcessEventOnWorkerThread``). ``HandleInputEvent()`` puts events in
 the ``event_queue_`` and the worker thread takes events from the
 ``event_queue_``. This processing happens independently of the main
 thread, so as not to slow down the browser.