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

Side by Side Diff: native_client_sdk/src/examples/api/vpn_provider/index.html

Issue 1731273002: ppapi: PPB_VpnProvider: Add a simple NaCl SDK example. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@vpn-ppapi
Patch Set: Created 4 years, 10 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
(Empty)
1 <!DOCTYPE html>
2 <html>
3 <!--
4 Copyright 2015 The Chromium Authors. All rights reserved.
binji 2016/02/24 19:23:09 nit: 2016
5 Use of this source code is governed by a BSD-style license that can be
6 found in the LICENSE file.
7 -->
8 <head>
9 <meta http-equiv="Pragma" content="no-cache">
10 <meta http-equiv="Expires" content="-1">
11 <title>VPN Provider example</title>
12 <script type="text/javascript" src="common.js"></script>
13 <script type="text/javascript" src="example.js"></script>
14 </head>
15 <!--
binji 2016/02/24 19:23:08 remove this, we only include this message in getti
16 For the SDK examples, we support several toolchains (e.g. PNaCl, newlib,
17 GLibC). In your own code, you'll likely just choose one toolchain (probably
18 PNaCl), and load that directly.
19
20 Rather than have each example repeat the same module loading code for each
21 toolchain it supports, we set custom data attributes on the body. Those
22 attributes are read by common.js to determine which toolchains are supported
23 for the example.
24 -->
25 <body data-name="vpn_provider"
binji 2016/02/24 19:23:08 this should be <body {{atrs}}>, take a look at som
26 data-tools="pnacl newlib glibc clang-newlib linux"
27 data-configs="Debug Release" data-path="{tc}/{config}">
28 <h1>VPN Provider example</h1>
29 <h2>Status: <code id="statusField">NO-STATUS</code></h2>
30 <!--
binji 2016/02/24 19:23:08 remove this comment
31 Just as in part1, the <embed> element will be wrapped inside the <div>
32 element with the id "listener". In part1, the embed was specified in HTML,
33 here the common.js module creates a new <embed> element and adds it to the
34 <div> for us.
35 -->
36 <div id="listener"></div>
37
38 <!--
39 This element will be populated with the messages that come from the NaCl
40 module. See example.js.
41 -->
42
43 <button id="load" onclick="load_me()" >Create</button>
binji 2016/02/24 19:23:09 Add documentation to the page explaining what it i
44 <button id="unload" onclick="unload_me()" disabled="true">Destroy</button>
45
46 <div id="log"></div>
47 </body>
48 </html>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698