@lightningjs/blits 1.30.0 → 1.30.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.editorconfig +7 -7
- package/.eslintignore +1 -1
- package/.eslintrc.cjs +65 -65
- package/.github/workflows/comment-lint-results.yml +124 -124
- package/.github/workflows/comment-test-results.yml +108 -108
- package/.github/workflows/deploy-docs.yml +27 -27
- package/.github/workflows/run-blits-tests.yml +141 -141
- package/.github/workflows/run-lint.yml +127 -127
- package/.husky/pre-commit +1 -1
- package/.vscode/extensions.json +7 -7
- package/.vscode/settings.json +9 -9
- package/CHANGELOG.md +1019 -1005
- package/COPYING +1 -0
- package/LICENSE +202 -202
- package/NOTICE +12 -12
- package/README.md +33 -33
- package/bin/index.js +8 -8
- package/blits.d.ts +6 -6
- package/docs/README.md +19 -19
- package/docs/_sidebar.md +37 -37
- package/docs/built-in/directives.md +50 -50
- package/docs/built-in/for-loop.md +203 -203
- package/docs/built-in/layout.md +168 -168
- package/docs/components/component_state.md +90 -90
- package/docs/components/computed_properties.md +45 -45
- package/docs/components/lifecycle_events.md +42 -42
- package/docs/components/methods.md +45 -45
- package/docs/components/props.md +56 -56
- package/docs/components/user_input.md +186 -186
- package/docs/components/utility_methods.md +320 -320
- package/docs/components/watchers.md +34 -34
- package/docs/essentials/application_root.md +19 -19
- package/docs/essentials/components.md +68 -68
- package/docs/essentials/displaying_images.md +67 -67
- package/docs/essentials/displaying_text.md +135 -135
- package/docs/essentials/element_attributes.md +195 -195
- package/docs/essentials/settings.md +117 -117
- package/docs/essentials/template_syntax.md +83 -83
- package/docs/getting_started/file_structure.md +58 -58
- package/docs/getting_started/getting_started.md +45 -45
- package/docs/getting_started/intro.md +20 -20
- package/docs/index.html +47 -47
- package/docs/performance/lazy-loading.md +161 -161
- package/docs/plugins/global_app_state.md +98 -98
- package/docs/plugins/language.md +172 -172
- package/docs/plugins/text-to-speech-announcer.md +119 -119
- package/docs/plugins/theme.md +176 -176
- package/docs/router/basics.md +175 -175
- package/docs/router/hooks.md +70 -70
- package/docs/router/transitions.md +146 -146
- package/docs/sidebar.json +171 -171
- package/docs/transitions_animations/transitions.md +150 -150
- package/index.d.ts +1099 -1099
- package/index.js +28 -28
- package/jsconfig.json +12 -12
- package/package.json +56 -56
- package/public/assets/fps_sprite.base64.js +1 -1
- package/scripts/postpublish.js +59 -59
- package/scripts/prepublishOnly.js +84 -84
- package/scripts/prepush.js +78 -78
- package/src/announcer/announcer.js +162 -162
- package/src/announcer/speechSynthesis.js +107 -107
- package/src/application.js +100 -100
- package/src/component/base/announcer.js +27 -27
- package/src/component/base/events.js +69 -69
- package/src/component/base/index.js +33 -33
- package/src/component/base/methods.js +244 -244
- package/src/component/base/router.js +41 -41
- package/src/component/base/timeouts_intervals.js +99 -99
- package/src/component/base/utils.js +72 -72
- package/src/component/setup/computed.js +48 -48
- package/src/component/setup/index.js +62 -62
- package/src/component/setup/input.js +30 -30
- package/src/component/setup/methods.js +37 -37
- package/src/component/setup/props.js +62 -62
- package/src/component/setup/props.test.js +238 -238
- package/src/component/setup/routes.js +42 -42
- package/src/component/setup/state.js +59 -59
- package/src/component/setup/watch.js +35 -35
- package/src/component.js +437 -437
- package/src/component.test.js +388 -388
- package/src/components/Circle.js +73 -73
- package/src/components/Circle.orig.js +31 -31
- package/src/components/FPScounter.js +1510 -1510
- package/src/components/FPScounter.orig.js +121 -121
- package/src/components/RouterView.js +81 -81
- package/src/components/RouterView.orig.js +54 -54
- package/src/components/Sprite.js +94 -94
- package/src/components/Sprite.orig.js +58 -58
- package/src/components/index.js +28 -28
- package/src/components/index.orig.js +28 -28
- package/src/constants.js +21 -21
- package/src/engine.js +1 -1
- package/src/engines/L3/element.js +744 -744
- package/src/engines/L3/element.test.js +579 -579
- package/src/engines/L3/fontLoader.js +38 -38
- package/src/engines/L3/index.js +7 -7
- package/src/engines/L3/launch.js +123 -123
- package/src/engines/L3/shaderLoader.js +12 -12
- package/src/engines/index.js +1 -1
- package/src/focus.js +90 -90
- package/src/helpers/deepEqualArray.js +50 -50
- package/src/helpers/deepEqualArray.test.js +127 -127
- package/src/helpers/fetchJson.js +34 -34
- package/src/helpers/sequence.js +26 -26
- package/src/launch.js +123 -123
- package/src/lib/blitsfileconverter/blitsfileconverter.js +52 -52
- package/src/lib/codegenerator/generator.js +788 -788
- package/src/lib/codegenerator/generator.test.js +3801 -3801
- package/src/lib/colors/colors.js +92 -92
- package/src/lib/colors/colors.test.js +290 -290
- package/src/lib/colors/htmlColors.js +168 -168
- package/src/lib/componentId.js +49 -49
- package/src/lib/componentId.test.js +84 -84
- package/src/lib/eventListeners.js +123 -123
- package/src/lib/eventListeners.test.js +236 -236
- package/src/lib/hooks.js +59 -59
- package/src/lib/lifecycle.js +85 -85
- package/src/lib/log.js +117 -117
- package/src/lib/precompiler/precompiler.js +73 -73
- package/src/lib/reactivity/effect.js +93 -93
- package/src/lib/reactivity/effect.test.js +35 -35
- package/src/lib/reactivity/reactive.js +208 -208
- package/src/lib/reactivity/reactive.test.js +27 -27
- package/src/lib/reactivityguard/computedprops.js +218 -218
- package/src/lib/symbols.js +108 -108
- package/src/lib/templateparser/parser.js +386 -386
- package/src/lib/templateparser/parser.test.js +1411 -1411
- package/src/lib/utils.js +27 -27
- package/src/plugin.js +27 -27
- package/src/plugins/appstate.js +26 -26
- package/src/plugins/index.js +20 -20
- package/src/plugins/language.js +152 -152
- package/src/plugins/log.js +25 -25
- package/src/plugins/theme.js +94 -94
- package/src/router/router.js +514 -514
- package/src/router/router.test.js +473 -473
- package/src/router/transitions/fadeIn.js +27 -27
- package/src/router/transitions/fadeInOut.js +33 -33
- package/src/router/transitions/index.js +21 -21
- package/src/router/transitions/slideIn.js +28 -28
- package/src/router/transitions/slideInOut.js +33 -33
- package/src/settings.js +40 -40
- package/vite/blitsFileConverter.js +67 -67
- package/vite/index.js +28 -28
- package/vite/msdfGenerator.js +269 -269
- package/vite/preCompiler.js +42 -42
- package/vite/reactivityGuard.js +45 -45
- package/vscode/data/template-attributes.json +589 -589
|
@@ -1,150 +1,150 @@
|
|
|
1
|
-
# Transitions
|
|
2
|
-
|
|
3
|
-
So far we have explored how to create components and draw elements on the screen. But everything has
|
|
4
|
-
been rather static so far.
|
|
5
|
-
|
|
6
|
-
We did learn how to _reactively_ change values and trigger rerenders based on that. So if you try the example below, you'll see that indeed our golden element changes position. But it just jumps from one place to another:
|
|
7
|
-
|
|
8
|
-
```js
|
|
9
|
-
export default Blits.Component('Gold', {
|
|
10
|
-
template: `
|
|
11
|
-
<Element color="gold" w="100" h="100" :x="$x" :y="$y" />
|
|
12
|
-
`,
|
|
13
|
-
state() {
|
|
14
|
-
return {
|
|
15
|
-
x: 0,
|
|
16
|
-
y: 0,
|
|
17
|
-
}
|
|
18
|
-
},
|
|
19
|
-
input: {
|
|
20
|
-
enter() {
|
|
21
|
-
this.x = this.x + 100
|
|
22
|
-
this.y = this.y + 50
|
|
23
|
-
}
|
|
24
|
-
},
|
|
25
|
-
```
|
|
26
|
-
|
|
27
|
-
Using _transitions_ we really make our App come alive.
|
|
28
|
-
|
|
29
|
-
## Applying a transition
|
|
30
|
-
|
|
31
|
-
Blits offers an easy and intuitive way to apply transitions. All you need to do is add the `.transition` modifier to a reactive attribute, and now whenever you change the value referenced in the attribute, it will automatically _smooth_ into the new value.
|
|
32
|
-
|
|
33
|
-
```js
|
|
34
|
-
export default Blits.Component('Gold', {
|
|
35
|
-
template: `
|
|
36
|
-
<Element color="gold" w="100" h="100" :x.transition="$x" :y.transition="$y" />
|
|
37
|
-
`,
|
|
38
|
-
state() {
|
|
39
|
-
return {
|
|
40
|
-
x: 0,
|
|
41
|
-
y: 0,
|
|
42
|
-
}
|
|
43
|
-
},
|
|
44
|
-
input: {
|
|
45
|
-
enter() {
|
|
46
|
-
this.x = this.x + 100
|
|
47
|
-
this.y = this.y + 50
|
|
48
|
-
}
|
|
49
|
-
},
|
|
50
|
-
```
|
|
51
|
-
|
|
52
|
-
If we try out the modified example above, you'll notice how much difference adding a simple transition makes.
|
|
53
|
-
|
|
54
|
-
When the `.transition`-modifier is added to a reactive attribute, a default `ease-in` transition with a duration of `300ms` is applied
|
|
55
|
-
|
|
56
|
-
## Customizing transitions
|
|
57
|
-
|
|
58
|
-
While the default transition will look pretty good out of the box and is great for quickly improving the look of your App, you may want to customize specific transitions.
|
|
59
|
-
|
|
60
|
-
Blits gives you full control over your transitions, with a simple to use format, right inside your template.
|
|
61
|
-
|
|
62
|
-
Instead of referencing your component's state variable directly, you can also supply an inline `object literal`` in the attribute with a `.transition`-modifier. This will allow you to pass a number of options to change the way the transition will work.
|
|
63
|
-
|
|
64
|
-
The transition object must have a `value` key, which references the state variable (or prop or computed property) that triggers the transition.
|
|
65
|
-
|
|
66
|
-
Furthermore, you can specify:
|
|
67
|
-
|
|
68
|
-
- `duration` - the duration of the transition in `ms`
|
|
69
|
-
- `delay` - the time in `ms` after which the transition should initiate
|
|
70
|
-
- `easing` - the easing function of the transition. Can be one of the default easing options listed below, or a custom `cubic-bezier` definition (i.e. `cubic-bezier(0,1.35,.99,-0.07)`).
|
|
71
|
-
|
|
72
|
-
```xml
|
|
73
|
-
<Element color="gold" w="100" h="100"
|
|
74
|
-
:x.transition="{value: $x, duration: 300, easing: 'ease-in-back', delay: 400}"
|
|
75
|
-
:y.transition="{value: $x, duration: 300, easing: 'cubic-bezier(1,-0.64,0.39,1.44)'}">
|
|
76
|
-
</Element>
|
|
77
|
-
```
|
|
78
|
-
|
|
79
|
-
Besides a reference to the `value`, you can also use dynamic values for the other keys in the transition object. This way you'll be able to dynamically control the delay, duration or easing function.
|
|
80
|
-
|
|
81
|
-
```xml
|
|
82
|
-
<Element color="gold" w="100" h="100"
|
|
83
|
-
:x.transition="{value: $x, duration: $dynamicDuration, delay: $dynamicDelay}">
|
|
84
|
-
</Element>
|
|
85
|
-
```
|
|
86
|
-
|
|
87
|
-
### Available easing functions
|
|
88
|
-
|
|
89
|
-
- `ease-in`
|
|
90
|
-
- `ease-out`
|
|
91
|
-
- `ease-in-out`
|
|
92
|
-
- `ease-in-sine`
|
|
93
|
-
- `ease-out-sine`
|
|
94
|
-
- `ease-in-out-sine`
|
|
95
|
-
- `ease-in-cubic`
|
|
96
|
-
- `ease-out-cubic`
|
|
97
|
-
- `ease-in-out-cubic`
|
|
98
|
-
- `ease-in-circ`
|
|
99
|
-
- `ease-out-circ`
|
|
100
|
-
- `ease-in-out-circ`
|
|
101
|
-
- `ease-in-back`
|
|
102
|
-
- `ease-out-back`
|
|
103
|
-
- `ease-in-out-back`
|
|
104
|
-
|
|
105
|
-
## Listening to transition events
|
|
106
|
-
|
|
107
|
-
Sometimes you may want to perform an action when a transition _ends_ or when it _starts_.
|
|
108
|
-
|
|
109
|
-
You can easily hook into these transition events by adding a `start` and `end` key to the transition object. Both values should be a function (or a reference to a `method` on your component).
|
|
110
|
-
|
|
111
|
-
The `start` function will be called when the transition actually starts (after a possible specified delay) and the `end` function is called as soon as the transition is finished.
|
|
112
|
-
|
|
113
|
-
```js
|
|
114
|
-
export default Blits.Component('Gold', {
|
|
115
|
-
template: `
|
|
116
|
-
<Element color="gold" w="100" h="100"
|
|
117
|
-
:x.transition="{value: $x, start: $transitionBegin, end: $transitionEnd}"
|
|
118
|
-
/>
|
|
119
|
-
`,
|
|
120
|
-
///
|
|
121
|
-
methods: {
|
|
122
|
-
transitionBegin() {
|
|
123
|
-
//
|
|
124
|
-
},
|
|
125
|
-
transitionEnd() {
|
|
126
|
-
//
|
|
127
|
-
},
|
|
128
|
-
}
|
|
129
|
-
```
|
|
130
|
-
|
|
131
|
-
It is also possible to keep track of the entire progress of a transition. Every frametick during a transition (ideally once every 16ms), the renderer reports the progress of the transition. You can hook into this event by specifying a `progress` key on the transition configuration object, with a function to excute.
|
|
132
|
-
|
|
133
|
-
This function is executed _every_ frametick, and receives the current progress and the previous progress as its arguments. The progress is indicated as a value between `0` and `1`, where 0 means start and 1 means finished.
|
|
134
|
-
|
|
135
|
-
```js
|
|
136
|
-
export default Blits.Component('Gold', {
|
|
137
|
-
template: `
|
|
138
|
-
<Element color="gold" w="100" h="100"
|
|
139
|
-
:x.transition="{value: $x, progress: $transitionProgress}"
|
|
140
|
-
/>
|
|
141
|
-
`,
|
|
142
|
-
///
|
|
143
|
-
methods: {
|
|
144
|
-
transitionProgress(progress, previousProgress) {
|
|
145
|
-
if(progress >= 0.5 && previousProgress < 0.5) {
|
|
146
|
-
// halfway through the transition
|
|
147
|
-
}
|
|
148
|
-
},
|
|
149
|
-
}
|
|
150
|
-
```
|
|
1
|
+
# Transitions
|
|
2
|
+
|
|
3
|
+
So far we have explored how to create components and draw elements on the screen. But everything has
|
|
4
|
+
been rather static so far.
|
|
5
|
+
|
|
6
|
+
We did learn how to _reactively_ change values and trigger rerenders based on that. So if you try the example below, you'll see that indeed our golden element changes position. But it just jumps from one place to another:
|
|
7
|
+
|
|
8
|
+
```js
|
|
9
|
+
export default Blits.Component('Gold', {
|
|
10
|
+
template: `
|
|
11
|
+
<Element color="gold" w="100" h="100" :x="$x" :y="$y" />
|
|
12
|
+
`,
|
|
13
|
+
state() {
|
|
14
|
+
return {
|
|
15
|
+
x: 0,
|
|
16
|
+
y: 0,
|
|
17
|
+
}
|
|
18
|
+
},
|
|
19
|
+
input: {
|
|
20
|
+
enter() {
|
|
21
|
+
this.x = this.x + 100
|
|
22
|
+
this.y = this.y + 50
|
|
23
|
+
}
|
|
24
|
+
},
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
Using _transitions_ we really make our App come alive.
|
|
28
|
+
|
|
29
|
+
## Applying a transition
|
|
30
|
+
|
|
31
|
+
Blits offers an easy and intuitive way to apply transitions. All you need to do is add the `.transition` modifier to a reactive attribute, and now whenever you change the value referenced in the attribute, it will automatically _smooth_ into the new value.
|
|
32
|
+
|
|
33
|
+
```js
|
|
34
|
+
export default Blits.Component('Gold', {
|
|
35
|
+
template: `
|
|
36
|
+
<Element color="gold" w="100" h="100" :x.transition="$x" :y.transition="$y" />
|
|
37
|
+
`,
|
|
38
|
+
state() {
|
|
39
|
+
return {
|
|
40
|
+
x: 0,
|
|
41
|
+
y: 0,
|
|
42
|
+
}
|
|
43
|
+
},
|
|
44
|
+
input: {
|
|
45
|
+
enter() {
|
|
46
|
+
this.x = this.x + 100
|
|
47
|
+
this.y = this.y + 50
|
|
48
|
+
}
|
|
49
|
+
},
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
If we try out the modified example above, you'll notice how much difference adding a simple transition makes.
|
|
53
|
+
|
|
54
|
+
When the `.transition`-modifier is added to a reactive attribute, a default `ease-in` transition with a duration of `300ms` is applied
|
|
55
|
+
|
|
56
|
+
## Customizing transitions
|
|
57
|
+
|
|
58
|
+
While the default transition will look pretty good out of the box and is great for quickly improving the look of your App, you may want to customize specific transitions.
|
|
59
|
+
|
|
60
|
+
Blits gives you full control over your transitions, with a simple to use format, right inside your template.
|
|
61
|
+
|
|
62
|
+
Instead of referencing your component's state variable directly, you can also supply an inline `object literal`` in the attribute with a `.transition`-modifier. This will allow you to pass a number of options to change the way the transition will work.
|
|
63
|
+
|
|
64
|
+
The transition object must have a `value` key, which references the state variable (or prop or computed property) that triggers the transition.
|
|
65
|
+
|
|
66
|
+
Furthermore, you can specify:
|
|
67
|
+
|
|
68
|
+
- `duration` - the duration of the transition in `ms`
|
|
69
|
+
- `delay` - the time in `ms` after which the transition should initiate
|
|
70
|
+
- `easing` - the easing function of the transition. Can be one of the default easing options listed below, or a custom `cubic-bezier` definition (i.e. `cubic-bezier(0,1.35,.99,-0.07)`).
|
|
71
|
+
|
|
72
|
+
```xml
|
|
73
|
+
<Element color="gold" w="100" h="100"
|
|
74
|
+
:x.transition="{value: $x, duration: 300, easing: 'ease-in-back', delay: 400}"
|
|
75
|
+
:y.transition="{value: $x, duration: 300, easing: 'cubic-bezier(1,-0.64,0.39,1.44)'}">
|
|
76
|
+
</Element>
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
Besides a reference to the `value`, you can also use dynamic values for the other keys in the transition object. This way you'll be able to dynamically control the delay, duration or easing function.
|
|
80
|
+
|
|
81
|
+
```xml
|
|
82
|
+
<Element color="gold" w="100" h="100"
|
|
83
|
+
:x.transition="{value: $x, duration: $dynamicDuration, delay: $dynamicDelay}">
|
|
84
|
+
</Element>
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
### Available easing functions
|
|
88
|
+
|
|
89
|
+
- `ease-in`
|
|
90
|
+
- `ease-out`
|
|
91
|
+
- `ease-in-out`
|
|
92
|
+
- `ease-in-sine`
|
|
93
|
+
- `ease-out-sine`
|
|
94
|
+
- `ease-in-out-sine`
|
|
95
|
+
- `ease-in-cubic`
|
|
96
|
+
- `ease-out-cubic`
|
|
97
|
+
- `ease-in-out-cubic`
|
|
98
|
+
- `ease-in-circ`
|
|
99
|
+
- `ease-out-circ`
|
|
100
|
+
- `ease-in-out-circ`
|
|
101
|
+
- `ease-in-back`
|
|
102
|
+
- `ease-out-back`
|
|
103
|
+
- `ease-in-out-back`
|
|
104
|
+
|
|
105
|
+
## Listening to transition events
|
|
106
|
+
|
|
107
|
+
Sometimes you may want to perform an action when a transition _ends_ or when it _starts_.
|
|
108
|
+
|
|
109
|
+
You can easily hook into these transition events by adding a `start` and `end` key to the transition object. Both values should be a function (or a reference to a `method` on your component).
|
|
110
|
+
|
|
111
|
+
The `start` function will be called when the transition actually starts (after a possible specified delay) and the `end` function is called as soon as the transition is finished.
|
|
112
|
+
|
|
113
|
+
```js
|
|
114
|
+
export default Blits.Component('Gold', {
|
|
115
|
+
template: `
|
|
116
|
+
<Element color="gold" w="100" h="100"
|
|
117
|
+
:x.transition="{value: $x, start: $transitionBegin, end: $transitionEnd}"
|
|
118
|
+
/>
|
|
119
|
+
`,
|
|
120
|
+
///
|
|
121
|
+
methods: {
|
|
122
|
+
transitionBegin() {
|
|
123
|
+
//
|
|
124
|
+
},
|
|
125
|
+
transitionEnd() {
|
|
126
|
+
//
|
|
127
|
+
},
|
|
128
|
+
}
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
It is also possible to keep track of the entire progress of a transition. Every frametick during a transition (ideally once every 16ms), the renderer reports the progress of the transition. You can hook into this event by specifying a `progress` key on the transition configuration object, with a function to excute.
|
|
132
|
+
|
|
133
|
+
This function is executed _every_ frametick, and receives the current progress and the previous progress as its arguments. The progress is indicated as a value between `0` and `1`, where 0 means start and 1 means finished.
|
|
134
|
+
|
|
135
|
+
```js
|
|
136
|
+
export default Blits.Component('Gold', {
|
|
137
|
+
template: `
|
|
138
|
+
<Element color="gold" w="100" h="100"
|
|
139
|
+
:x.transition="{value: $x, progress: $transitionProgress}"
|
|
140
|
+
/>
|
|
141
|
+
`,
|
|
142
|
+
///
|
|
143
|
+
methods: {
|
|
144
|
+
transitionProgress(progress, previousProgress) {
|
|
145
|
+
if(progress >= 0.5 && previousProgress < 0.5) {
|
|
146
|
+
// halfway through the transition
|
|
147
|
+
}
|
|
148
|
+
},
|
|
149
|
+
}
|
|
150
|
+
```
|