Skip to content

Commit a63cdb4

Browse files
committed
chore(docs): add full screen viewer links to open demos in new tab
1 parent 3faea24 commit a63cdb4

File tree

2 files changed

+11
-3
lines changed

2 files changed

+11
-3
lines changed

docs/guide/js/bundler.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,3 +24,5 @@ Here, the VTK.wasm bundle is downloaded in the browser directly from the Gitlab
2424
## Result
2525

2626
<iframe src="/vtk-wasm/demo/simple-app/index.html" style="width: 100%; height: 25vh; border: none;"></iframe>
27+
28+
[Full Screen Viewer](../../demo/simple-app/index.html){target="_blank"}

docs/guide/js/plain.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,6 @@
22

33
The following examples rely on loading the `vtk.umd.js` bundle from a CDN. Also to mainly focus on the initialization part, we've externalized the JS/WASM code since that part does not change.
44

5-
<iframe src="/vtk-wasm/demo/plain-javascript.html" style="width: 100%; height: 40vh; border: none;"></iframe>
6-
75
## Load WASM as module
86

97
In this example we pre-load the WASM module and therefore we don't need to provide any URL for loading it when creating the __vtk__ namespace.
@@ -17,14 +15,17 @@ In this example we pre-load the WASM module and therefore we don't need to provi
1715

1816
In this example, since we didn't load the WASM module, we need to specify from where it should be loaded.
1917

20-
2118
In this context we provide the URL where the WASM bundle can be found and used from.
2219

2320
::: code-group
2421
<<< ../../public/demo/plain-javascript.html
2522
<<< ../../public/demo/example.js
2623
:::
2724

25+
<iframe src="/vtk-wasm/demo/plain-javascript.html" style="width: 100%; height: 40vh; border: none;"></iframe>
26+
27+
[Full Screen Viewer](../../demo/plain-javascript.html){target="_blank"}
28+
2829
## Defer WASM loading with annotation
2930

3031
In this example we tag the script to autoload WASM directly from the VTK repository's package registry and create a global vtk namespace. You can customize the wasm architecture and version by changing the data-url.
@@ -34,6 +35,11 @@ In this example we tag the script to autoload WASM directly from the VTK reposit
3435
<<< ../../public/demo/example.js
3536
:::
3637

38+
<iframe src="/vtk-wasm/demo/plain-javascript-annotation-wasm-registry.html" style="width: 100%; height: 40vh; border: none;"></iframe>
39+
40+
[Full Screen Viewer](../../demo/plain-javascript-annotation-wasm-registry.html){target="_blank"}
41+
42+
3743
## Configuration options
3844

3945
The method `createNamespace(url, config)` takes two arguments. The first one is used to specify the base directory where the wasm file from VTK will be find. When the module is loaded, the __url__ parameter could be skipped. For the __config__ it is aimed to tune how you would like your WASM environement to behave. The following sections cover the various options and what it means.

0 commit comments

Comments
 (0)