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

Side by Side Diff: native_client_sdk/doc_generated/glossary.html

Issue 476793002: Per P0 reqs add launch pts + make download obvious. Also misc cpy edits. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: CL synced with master. Created 6 years, 4 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 unified diff | Download patch
OLDNEW
1 {{+bindTo:partials.standard_nacl_article}} 1 {{+bindTo:partials.standard_nacl_article}}
2 2
3 <section id="glossary"> 3 <section id="glossary">
4 <span id="id1"></span><h1 id="glossary"><span id="id1"></span>Glossary</h1> 4 <span id="id1"></span><h1 id="glossary"><span id="id1"></span>Glossary</h1>
5 <p>This glossary defines terms and names commonly used throughout the Native Cli ent 5 <p>This glossary defines terms and names commonly used throughout the Native Cli ent
6 documentation.</p> 6 documentation.</p>
7 <dl class="docutils"> 7 <dl class="docutils">
8 <dt>asynchronous programming</dt> 8 <dt>asynchronous programming</dt>
9 <dd>In the asynchronous programming model, function calls are executed and retur n 9 <dd>In the asynchronous programming model, function calls are executed and retur n
10 immediately without waiting for a response. Using this model, function calls 10 immediately without waiting for a response. Using this model, function calls
11 are non-blocking; the web browser continues its main thread of execution 11 are non-blocking; the web browser continues its main thread of execution
12 and gets notified of asynchronous call completion through callbacks or some 12 and gets notified of asynchronous call completion through callbacks or some
13 other mechanism.</dd> 13 other mechanism.</dd>
14 <dt>focus events</dt> 14 <dt>focus events</dt>
15 <dd>Events that indicate whether certain parts of a web page are 15 <dd>Events that indicate whether certain parts of a web page are
16 in or out of focus.</dd> 16 in or out of focus.</dd>
17 <dt>input events</dt> 17 <dt>input events</dt>
18 <dd>Events that occur when an input device (such as keyboard or mouse) 18 <dd>Events that occur when an input device (such as keyboard or mouse)
19 is used to interact with an module instance.</dd> 19 is used to interact with an module instance.</dd>
20 <dt>instance</dt> 20 <dt>instance</dt>
21 <dd>A rectangle on a web page that is managed by a Native Client module (the 21 <dd>A rectangle on a web page that is managed by a Native Client module (the
22 rectangle can have <code>width=0</code> and <code>height=0</code>, which means t hat nothing is 22 rectangle can have <code>width=0</code> and <code>height=0</code>, which means t hat nothing is
23 drawn on the page).</dd> 23 drawn on the page).</dd>
24 <dt>manifest file</dt> 24 <dt>manifest file</dt>
25 <dd>A file containing metadata or information about accompanying files.</dd> 25 <dd>A file containing metadata or information about accompanying files.</dd>
26 <dt>message events</dt> 26 <dt>message events</dt>
27 <dd>Events used to pass data between JavaScript and the Native Client 27 <dd>Events used to pass data between JavaScript and the Native Client
28 module (see the <a class="reference internal" href="/native-client/devguide/codi ng/message-system.html"><em>Messaging System</em></a> chapter).</dd> 28 module (see the <a class="reference internal" href="/native-client/devguide/codi ng/message-system.html"><em>Messaging System</em></a> section).</dd>
29 <dt>module</dt> 29 <dt>module</dt>
30 <dd>Depending on context, &#8220;module&#8221; may mean one of two things. First , it may be a 30 <dd>Depending on context, &#8220;module&#8221; may mean one of two things. First , it may be a
31 general short-term for for &#8220;Native Client module&#8221;&#8212;compiled C/C ++ code 31 general short-term for for &#8220;Native Client module&#8221;&#8212;compiled C/C ++ code
32 produced with a Native Client toolchain (for example PNaCl). See 32 produced with a Native Client toolchain (for example PNaCl). See
33 <a class="reference internal" href="/native-client/overview.html#link-how-nacl-w orks"><em>How Native Client works</em></a> for more details. 33 <a class="reference internal" href="/native-client/overview.html#link-how-nacl-w orks"><em>How Native Client works</em></a> for more details.
34 Second, it may refer to a concrete implementation of the <a class="reference ext ernal" href="/native-client/pepper_stable/cpp/classpp_1_1_module">pp::Module cla ss</a> for some Native 34 Second, it may refer to a concrete implementation of the <a class="reference ext ernal" href="/native-client/pepper_stable/cpp/classpp_1_1_module">pp::Module cla ss</a> for some Native
35 Client module.</dd> 35 Client module.</dd>
36 <dt>progress events</dt> 36 <dt>progress events</dt>
37 <dd>Events generated by the Native Client runtime system during the 37 <dd>Events generated by the Native Client runtime system during the
38 module loading process.</dd> 38 module loading process.</dd>
39 <dt>Var</dt> 39 <dt>Var</dt>
40 <dd>An object in a Native Client module that corresponds to a JavaScript 40 <dd>An object in a Native Client module that corresponds to a JavaScript
41 variable.</dd> 41 variable.</dd>
42 <dt>view change events</dt> 42 <dt>view change events</dt>
43 <dd>Events that occur when a change in the browser affects the 43 <dd>Events that occur when a change in the browser affects the
44 module instance (such as resizing the browser window or going to 44 module instance (such as resizing the browser window or going to
45 and from fullscreen mode).</dd> 45 and from fullscreen mode).</dd>
46 <dt>web workers</dt> 46 <dt>web workers</dt>
47 <dd><a class="reference external" href="http://en.wikipedia.org/wiki/Web_Workers ">Web workers</a> provide a 47 <dd><a class="reference external" href="http://en.wikipedia.org/wiki/Web_Workers ">Web workers</a> provide a
48 mechanism for running heavy-weight JavaScript code on background threads 48 mechanism for running heavy-weight JavaScript code on background threads
49 so that the main web page can continue to respond to user interaction. 49 so that the main web page can continue to respond to user interaction.
50 Web pages interact with web workers by using <code>postMessage()</code> to send 50 Web pages interact with web workers by using <code>postMessage()</code> to send
51 messages. The way a web page interacts with a Native Client module 51 messages. The way a web page interacts with a Native Client module
52 is analogous to the way it interacts with web workers.</dd> 52 is analogous to the way it interacts with web workers.</dd>
53 </dl> 53 </dl>
54 </section> 54 </section>
55 55
56 {{/partials.standard_nacl_article}} 56 {{/partials.standard_nacl_article}}
OLDNEW
« no previous file with comments | « native_client_sdk/doc_generated/devguide/tutorial/tutorial-part1.html ('k') | native_client_sdk/doc_generated/index.html » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698