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

native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="view-change-focus-and-input-events">
 <span id="view-focus-input-events"></span><h1 id="view-change-focus-and-input-events"><span id="view-focus-input-events"></span>View Change, Focus, and Input Events</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#overview" id="id2">Overview</a></li>
 <li><p class="first"><a class="reference internal" href="#handling-browser-events" id="id3">Handling browser events</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#didchangeview" id="id4">DidChangeView()</a></li>
@@ skipping 18 matching lines @@
 event.  The <code>mouse_lock</code> example is used to illustrate how your module
 can react to view change events. You can find these examples in the
 <code>/examples/api/input_events</code> and <code>/examples/api/mouse_lock</code>
 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 <code>pi_generator</code> example in
 <code>/examples/demo/pi_generator</code> uses ppapi_simple to manage view
 change events and 2D graphics.</p>
 <section id="overview">
 <h2 id="overview">Overview</h2>
-<p>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&#8217;s instance to the module. Native Client modules can
-override certain functions in the <a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_instance">pp::Instance</a>
-class to handle input and browser events. These functions are listed in
-the table below:</p>
+<p>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&#8217;s instance to the module. Native Client modules can
+override certain functions in the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_instance">pp::Instance</a> class to handle input
+and browser events. These functions are listed in the table below:</p>
 <table border="1" class="docutils">
 <colgroup>
 </colgroup>
 <thead valign="bottom">
 <tr class="row-odd"><th class="head">Function</th>
 <th class="head">Event</th>
 <th class="head">Use</th>
 </tr>
 </thead>
 <tbody valign="top">
@@ skipping 88 matching lines @@
 prior to overriding this
 function.</td>
 <td>An implementation of
 this function
 examines the input
 event type and
 branches accordingly.</td>
 </tr>
 </tbody>
 </table>
-<p>These interfaces are found in the <a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_instance">pp::Instance class</a>.
-The sections below provide examples of how to handle these events.</p>
+<p>These interfaces are found in the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_instance">pp::Instance class</a>.  The sections below
+provide examples of how to handle these events.</p>
 </section><section id="handling-browser-events">
 <h2 id="handling-browser-events">Handling browser events</h2>
 <section id="didchangeview">
 <h3 id="didchangeview">DidChangeView()</h3>
 <p>In the <code>mouse_lock</code> example, <code>DidChangeView()</code> checks the previous size
 of instance&#8217;s rectangle versus the new size.  It also compares
 other state such as whether or not the app is running in full screen mode.
 If none of the state has actually changed, no action is needed.
 However, if the size of the view or other state has changed, it frees the
 old graphics context and allocates a new one.</p>
@@ skipping 16 matching lines @@
   is_context_bound_ = BindGraphics(device_context_);
   // ...
 
   // Remember if we are fullscreen or not
   was_fullscreen_ = view.IsFullscreen();
   // ...
 }
 </pre>
 <p>For more information about graphics contexts and how to manipulate images, see:</p>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_image_data">pp::ImageData class</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_graphics2_d">pp::Graphics2D class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_image_data">pp::ImageData class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_graphics2_d">pp::Graphics2D class</a></li>
 </ul>
 </section><section id="didchangefocus">
 <h3 id="didchangefocus">DidChangeFocus()</h3>
 <p><code>DidChangeFocus()</code> is called when you click inside or outside of a
 module&#8217;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.</p>
 <pre class="prettyprint">
 void DidChangeFocus(bool focus) {
@@ skipping 20 matching lines @@
   explicit InputEventInstance(PP_Instance instance)
       : 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);
   }
   // ...
 };
 </pre>
 <p><code>RequestInputEvents()</code> and <code>RequestFilteringInputEvents()</code> 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 <a class="reference external" href="https://developers.google.com/native-client/dev/pepperc/group___enums.html#gafe68e3c1031daa4a6496845ff47649cd">PP_InputEvent_Class</a>
-enumeration in <a class="reference external" href="https://developers.google.com/native-client/dev/pepperc/ppb__input__event_8h">ppb_input_event.h</a>.</p>
+combination of flags that identify the class of events that the instance is
+requesting to receive. Input event classes are defined in the
+<a class="reference external" href="/native-client/pepper_stable/c/group___enums.html#gafe68e3c1031daa4a6496845ff47649cd">PP_InputEvent_Class</a>
+enumeration in <a class="reference external" href="/native-client/pepper_stable/c/ppb__input__event_8h">ppb_input_event.h</a>.</p>
 </section><section id="determining-and-branching-on-event-types">
 <h3 id="determining-and-branching-on-event-types">Determining and branching on event types</h3>
-<p>In a typical implementation, the <code>HandleInputEvent()</code> function
-determines the type of each event using the <code>GetType()</code> function found
-in the <code>InputEvent</code> class. The <code>HandleInputEvent()</code> function then uses a
-switch statement to branch on the type of input event. Input events
-are defined in the <a class="reference external" href="https://developers.google.com/native-client/dev/pepperc/group___enums.html#gaca7296cfec99fcb6646b7144d1d6a0c5">PP_InputEvent_Type</a>
-enumeration in <a class="reference external" href="https://developers.google.com/native-client/dev/pepperc/ppb__input__event_8h">ppb_input_event.h</a>.</p>
+<p>In a typical implementation, the <code>HandleInputEvent()</code> function determines the
+type of each event using the <code>GetType()</code> function found in the <code>InputEvent</code>
+class. The <code>HandleInputEvent()</code> function then uses a switch statement to
+branch on the type of input event. Input events are defined in the
+<a class="reference external" href="/native-client/pepper_stable/c/group___enums.html#gaca7296cfec99fcb6646b7144d1d6a0c5">PP_InputEvent_Type</a>
+enumeration in <a class="reference external" href="/native-client/pepper_stable/c/ppb__input__event_8h">ppb_input_event.h</a>.</p>
 <pre class="prettyprint">
 virtual bool HandleInputEvent(const pp::InputEvent&amp; event) {
   Event* event_ptr = NULL;
   switch (event.GetType()) {
     case PP_INPUTEVENT_TYPE_UNDEFINED:
       break;
     case PP_INPUTEVENT_TYPE_MOUSEDOWN:
     case PP_INPUTEVENT_TYPE_MOUSEUP:
     case PP_INPUTEVENT_TYPE_MOUSEMOVE:
     case PP_INPUTEVENT_TYPE_MOUSEENTER:
@@ skipping 56 matching lines @@
   }
   event_queue_.Push(event_ptr);
   return true;
 }
 </pre>
 <p>Notice that the generic <code>InputEvent</code> received by <code>HandleInputEvent()</code> is
 converted into a specific type after the event type is
 determined.  The event types handled in the example code are
 <code>MouseInputEvent</code>, <code>WheelInputEvent</code>, and <code>KeyboardInputEvent</code>.
 There are also <code>TouchInputEvents</code>.  For the latest list of event types,
-see the <a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_input_event">InputEvent documentation</a>.
+see the <a class="reference external" href="/native-client/pepper_stable/c/classpp_1_1_input_event">InputEvent documentation</a>.
 For reference information related to the these event classes, see the
 following documentation:</p>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_mouse_input_event">pp::MouseInputEvent class</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_wheel_input_event">pp::WheelInputEvent class</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_keyboard_input_event">pp::KeyboardInputEvent class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/c/classpp_1_1_mouse_input_event">pp::MouseInputEvent class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/c/classpp_1_1_wheel_input_event">pp::WheelInputEvent class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/c/classpp_1_1_keyboard_input_event">pp::KeyboardInputEvent class</a></li>
 </ul>
 </section><section id="threading-and-blocking">
 <h3 id="threading-and-blocking">Threading and blocking</h3>
 <p><code>HandleInputEvent()</code> in this example runs on the main module thread.
 However, the bulk of the work happens on a separate worker thread (see
 <code>ProcessEventOnWorkerThread</code>). <code>HandleInputEvent()</code> puts events in
 the <code>event_queue_</code> and the worker thread takes events from the
 <code>event_queue_</code>. This processing happens independently of the main
 thread, so as not to slow down the browser.</p>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}