blob: 2dd2f500a89102fe49048d905eea87722d541861 [file] [log] [blame]
<!DOCTYPE html>
<html>
<!--
Copyright (c) 2013 The Chromium Authors. All rights reserved.
Use of this source code is governed by a BSD-style license that can be
found in the LICENSE file.
-->
<head>
<meta http-equiv="Pragma" content="no-cache">
<meta http-equiv="Expires" content="-1">
<title>{{title}}</title>
<script type="text/javascript" src="common.js"></script>
<script type="text/javascript" src="example.js"></script>
</head>
<!--
For the SDK examples, we support several toolchains (e.g. PNaCl, newlib,
GLibC). In your own code, you'll likely just choose one toolchain (probably
PNaCl), and load that directly.
Rather than have each example repeat the same module loading code for each
toolchain it supports, we set custom data attributes on the body. Those
attributes are read by common.js to determine which toolchains are supported
for the example.
-->
<body {{attrs}}>
<h1>{{title}}</h1>
<h2>Status: <code id="statusField">NO-STATUS</code></h2>
<!--
Just as in part1, the <embed> element will be wrapped inside the <div>
element with the id "listener". In part1, the embed was specified in HTML,
here the common.js module creates a new <embed> element and adds it to the
<div> for us.
-->
<div id="listener"></div>
<!--
This element will be populated with the messages that come from the NaCl
module. See example.js.
-->
<div id="log"></div>
</body>
</html>