eeeb4b7de2
* Use correct FBO to output * custom_3d_three-d web * Update .gitignore * Do not free the FBO * Use three-d 0.13 * ThreeDApp * Only construct model and camera once * Clean-up and docs * Web build instructions * Remove unused dependencies * Update Cargo.lock * Fix build * More fixes * omg
38 lines
1.7 KiB
HTML
38 lines
1.7 KiB
HTML
<html>
|
|
<head>
|
|
<meta content="text/html;charset=utf-8" http-equiv="Content-Type"/>
|
|
</head>
|
|
<body>
|
|
<canvas id="my" style="position: absolute;top:0;bottom: 0;left: 0;right: 0;margin:auto;"></canvas>
|
|
<!-- Note the usage of `type=module` here as this is an ES6 module -->
|
|
<script type="module">
|
|
// Use ES module import syntax to import functionality from the module
|
|
// that we have compiled.
|
|
//
|
|
// Note that the `default` import is an initialization function which
|
|
// will "boot" the module and make it ready to use. Currently browsers
|
|
// don't support natively imported WebAssembly as an ES module, but
|
|
// eventually the manual initialization won't be required!
|
|
import init from './pkg/custom_3d_three_d.js';
|
|
|
|
async function run() {
|
|
// First up we need to actually load the wasm file, so we use the
|
|
// default export to inform it where the wasm file is located on the
|
|
// server, and then we wait on the returned promise to wait for the
|
|
// wasm to be loaded.
|
|
// It may look like this: `await init('./pkg/without_a_bundler_bg.wasm');`,
|
|
// but there is also a handy default inside `init` function, which uses
|
|
// `import.meta` to locate the wasm file relatively to js file
|
|
//
|
|
// Note that instead of a string here you can also pass in an instance
|
|
// of `WebAssembly.Module` which allows you to compile your own module.
|
|
// Also note that the promise, when resolved, yields the wasm module's
|
|
// exports which is the same as importing the `*_bg` module in other
|
|
// modes
|
|
await init('./pkg/custom_3d_three_d_bg.wasm');
|
|
}
|
|
|
|
run();
|
|
</script>
|
|
</body>
|
|
</html>
|