You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Why on(), off(), feature() methods fail after constructor call?
10
+
11
+
The Vizzu constructor has to load Vizzu's WebAssembly module asynchronously to prevent blocking the whole page.
12
+
Because of this, any method except `animate()` will throw an exception while the library is not initialized.
13
+
14
+
There is an `initializing` promise in the Vizzu class, which will resolve when initialization is finished. You can call all methods after
15
+
this promise is resolved.
16
+
17
+
## How to load data from CSV into Vizzu?
18
+
19
+
This example reads the data from a CSV: https://lib.vizzuhq.com/0.3.0/content/howtos/csv-input/
20
+
21
+
You can find the source here; the CSV loading part is in the csv-input.js file: https://github.com/vizzuhq/vizzu-lib-doc/tree/main/docs/0.3.0/content/howtos/csv-input
Copy file name to clipboardExpand all lines: docs/content/tutorial/0-intro.md
+5-11Lines changed: 5 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,26 +48,20 @@ chart.initializing.then(
48
48
)
49
49
```
50
50
51
-
### Working with Bundlers, changing the location of the WASM module
51
+
### Working with bundlers & frameworks
52
52
53
53
The published Vizzu package contains a Javascript (*vizzu.min.js*) and a
54
-
WebAssembly (*cvizzu.wasm*) module. By default, the Javascript module tries to
55
-
load the wasm module from the same path, it was imported from.
54
+
WebAssembly (*cvizzu.wasm*) module. By default, the Javascript module tries to load the wasm module from the same path it was imported from.
56
55
57
-
This behaviour won't work well with bundlers, if they move the wasm file to a
58
-
different folder. To handle this case, the location of the wasm module can be
59
-
set for the library.
56
+
This behavior won't work with bundlers if they move the wasm file to a different folder. To handle this issue, you can manually set the wasm module's location.
60
57
61
58
```Javascript { "run": false }
62
59
Vizzu.options({ wasmUrl:"/path/to/cvizzu.wasm" })
63
60
```
64
61
65
-
> Note: this should be set before the Vizzu constructor called, since it will
66
-
> load the wasm module.
62
+
> Note: you should set this path before the Vizzu constructor is called because it loads the wasm module.
67
63
68
-
Different Bundlers will need additional bundler specific settings to recognize
69
-
the wasm file as dependency and to handle it correctly. For setting up Vizzu
70
-
with a specific bundler or framework, see the corresponding howto/example below:
64
+
Different bundlers will need additional, specific settings to recognize the wasm file as a dependency and handle it correctly. For setting up Vizzu with a specific bundler or framework, check the corresponding how-to/example below:
Copy file name to clipboardExpand all lines: docs/content/tutorial/10-filtering.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,14 +19,14 @@ chart.animate({
19
19
})
20
20
```
21
21
22
-
Now we add a cross-filter that includes items from both the Genres and the Types dimensions. This way we override the filter from the previous state. If we weren't update the filter, Vizzu would use it in subsequent states.
22
+
Now we add a cross-filter that includes items from both the Genres and the Kinds dimensions. This way we override the filter from the previous state. If we weren't update the filter, Vizzu would use it in subsequent states.
23
23
24
24
```javascript { "title": "Filter by two dimensions" }
0 commit comments