@@ -19,8 +19,8 @@ defmodule Scenic.Script do
19
19
20
20
Simply put, Scenic.Script produces a list of static drawing commands that are
21
21
sent, unmodified, to the drivers through the ViewPort. These scripts are
22
- generated for you when you use push_graph, or you can create them yourself
23
- by using this api.
22
+ generated for you when you use `Scenic.Scene. push_graph/3` , or you can create
23
+ them yourself by using this api.
24
24
25
25
If you use Scenic.Script directly, you can create more complicated and/or
26
26
reusable graphics than you could by using Graphs alone.
@@ -31,17 +31,17 @@ defmodule Scenic.Script do
31
31
that which changes frequently. When a graph is pushed to the ViewPort, the
32
32
entire thing is compiled into a script, which is sent as a whole to the Drivers.
33
33
34
- If that graph references a script tho , only the reference is sent, not the contents
35
- of the script. This means you can modify the graph frequently without sending
36
- the contents of the scripts.
34
+ However if that graph references a script, only the reference to the script is
35
+ sent, not the contents of the script. This means you can modify the graph
36
+ frequently without sending the contents of the scripts.
37
37
38
38
The opposite is also true. You can generate and push the scripts frequently
39
39
without causing the graphs that reference them to be recompiled or resent.
40
40
41
- And example of this might be a graph that implements a chart of some sort.
42
-
43
- The contents of the chart could be a script that is updated as new data comes
44
- in without needed all the chrome around it to be recompiled or sent .
41
+ An example of this might be a graph that implements a chart of some sort. The
42
+ contents of the chart could be a script that is updated as new data comes in
43
+ without needing all the chrome around it to be recompiled or sent for every
44
+ update .
45
45
46
46
## API Patterns
47
47
0 commit comments