Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(164)

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

Issue 254033002: [NaCl SDK Docs] Remove links to developers.google.com (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: . Created 6 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html
diff --git a/native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html b/native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html
index 793e57b7c546b5402e55b4ace4482f21639f77b6..8dc052a4d1770c3b7b407a063bc0b314c4adcaf6 100644
--- a/native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html
+++ b/native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html
@@ -36,18 +36,16 @@ boiler plate. The <code>pi_generator</code> example in
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>
@@ -156,8 +154,8 @@ 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">
@@ -194,8 +192,8 @@ void MouseLockInstance::DidChangeView(const pp::View&amp; view) {
</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>
@@ -236,18 +234,18 @@ class InputEventInstance : public pp::Instance {
};
</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;
@@ -324,13 +322,13 @@ 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>

Powered by Google App Engine
This is Rietveld 408576698