glossary.html 3.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364
  1. {{+bindTo:partials.standard_nacl_article}}
  2. <b><font color="#cc0000">
  3. NOTE:
  4. Deprecation of the technologies described here has been announced
  5. for platforms other than ChromeOS.<br/>
  6. Please visit our
  7. <a href="/native-client/migration">migration guide</a>
  8. for details.
  9. </font></b>
  10. <hr/><section id="id1">
  11. <h1 id="id1">Glossary</h1>
  12. <p>This glossary defines terms and names commonly used throughout the Native Client
  13. documentation.</p>
  14. <dl class="docutils">
  15. <dt>asynchronous programming</dt>
  16. <dd>In the asynchronous programming model, function calls are executed and return
  17. immediately without waiting for a response. Using this model, function calls
  18. are non-blocking; the web browser continues its main thread of execution
  19. and gets notified of asynchronous call completion through callbacks or some
  20. other mechanism.</dd>
  21. <dt>focus events</dt>
  22. <dd>Events that indicate whether certain parts of a web page are
  23. in or out of focus.</dd>
  24. <dt>input events</dt>
  25. <dd>Events that occur when an input device (such as keyboard or mouse)
  26. is used to interact with an module instance.</dd>
  27. <dt>instance</dt>
  28. <dd>A rectangle on a web page that is managed by a Native Client module (the
  29. rectangle can have <code>width=0</code> and <code>height=0</code>, which means that nothing is
  30. drawn on the page).</dd>
  31. <dt>manifest file</dt>
  32. <dd>A file containing metadata or information about accompanying files.</dd>
  33. <dt>message events</dt>
  34. <dd>Events used to pass data between JavaScript and the Native Client
  35. module (see the <a class="reference internal" href="/native-client/devguide/coding/message-system.html"><em>Messaging System</em></a> section).</dd>
  36. <dt>module</dt>
  37. <dd>Depending on context, &#8220;module&#8221; may mean one of two things. First, it may be a
  38. general short-term for for &#8220;Native Client module&#8221;&#8212;compiled C/C++ code
  39. produced with a Native Client toolchain (for example PNaCl). See
  40. <a class="reference internal" href="/native-client/overview.html#link-how-nacl-works"><em>How Native Client works</em></a> for more details.
  41. Second, it may refer to a concrete implementation of the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_module">pp::Module class</a> for some Native
  42. Client module.</dd>
  43. <dt>progress events</dt>
  44. <dd>Events generated by the Native Client runtime system during the
  45. module loading process.</dd>
  46. <dt>Var</dt>
  47. <dd>An object in a Native Client module that corresponds to a JavaScript
  48. variable.</dd>
  49. <dt>view change events</dt>
  50. <dd>Events that occur when a change in the browser affects the
  51. module instance (such as resizing the browser window or going to
  52. and from fullscreen mode).</dd>
  53. <dt>web workers</dt>
  54. <dd><a class="reference external" href="http://en.wikipedia.org/wiki/Web_Workers">Web workers</a> provide a
  55. mechanism for running heavy-weight JavaScript code on background threads
  56. so that the main web page can continue to respond to user interaction.
  57. Web pages interact with web workers by using <code>postMessage()</code> to send
  58. messages. The way a web page interacts with a Native Client module
  59. is analogous to the way it interacts with web workers.</dd>
  60. </dl>
  61. </section>
  62. {{/partials.standard_nacl_article}}