-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathindex.html
338 lines (270 loc) · 10.6 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Redux</title>
<meta name="description" content="Why Redux">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/black.css" id="theme">
<style>
.reveal img { max-width: 80%; }
</style>
<!-- Code syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section data-markdown>
<script type="text/template">
# REDUX
**A sane approach to managing data flow in complex web applications**
</script>
</section>
<section data-markdown>
<script type="text/template">
Web apps have become very complex.
"At some point you no longer know what happens in your app. You no longer control when, why, and how the state is updated."
</script>
</section>
<section data-markdown>
<script type="text/template">
Before talking about redux lets get some background.
</script>
</section>
<section>
<section data-markdown>
<script type="text/template">
Games have complex state that changes frequently based on simulations rules and user input.
</script>
</section>
<section data-markdown>
<script type="text/template">
####Games mange updating state via a game loop:
- Starting state
- Gather user input
- Update state based on user input and simulation rules
- Render visual representation to screen
- Rinse, wash, repeat - 60 times a second!
> <!-- .element: class="fragment" -->
> Can we write web apps the way we write games?
</script>
</section>
<section data-markdown>
<script type="text/template">
###Enter React.js
Unlike other MV\* frameworks since Backbone, React is a game changer because *it lets us write web apps the way we write games.* We can throw a new state at the DOM as often as we please.
> <!-- .element: class="fragment" -->
> This means we need to think about building applications differently.
</script>
</section>
<section data-markdown>
<script type="text/template">
###It's the **data flow** that matters.
(The UI is a side effect; your app should be able to run from the command line.)
> <!-- .element: class="fragment" -->
> How do we control data flow?
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## FLUX
"Flux eschews MVC in favor of a unidirectional data flow"
</script>
</section>
<section data-markdown>
<script type="text/template">
Before:
</script>
</section>
<section data-markdown>
<script type="text/template">
After:
Unidirectional flow:
1. *Stores* hold your state
2. *Views* listen to and render that state
3. Events are represented as *actions*
4. Actions get *dispatched* to the stores
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## Back to redux
Redux is a pure, functional implementaiton of flux
</script>
</section>
<section data-markdown>
<script type="text/template">
> `(state, action) -> state`
</script>
</section>
<section data-markdown>
<script type="text/template">
- Redux doesn't have a Dispatcher or support many stores. Instead, there is just a single store with a single root reducing function.
- As your app grows, instead of adding stores, you split the root reducer into smaller reducers independently operating on the different parts of the state tree.
- By using only pure functions, everything is predictable
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## Let's see some code
</script>
</section>
<section data-markdown>
<script type="text/template">
```
// The reducer
function counter(state = 0, action) {
switch (action.type) {
case 'INCREMENT':
return state + action.amount;
case 'DECREMENT':
return state - action.amount;
default:
return state;
}
}
// The store bound with your reducer
let store = Redux.createStore(counter);
```
</script>
</section>
<section data-markdown>
<script type="text/template">
```
// Side effects (this is where you could pass your data into react)
store.subscribe(() =>
console.log(store.getState())
);
// Send some actions
store.dispatch({ type: 'INCREMENT', amount: 1 });
// 1
store.dispatch({ type: 'INCREMENT', amount: 3 });
// 4
store.dispatch({ type: 'DECREMENT', amount: 2 });
// 2
```
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
##Why Redux?
1. "A predictable state container" <!-- .element: class="fragment" -->
- Single source of truth
- Consistent and portable
2. Separate presentation layer from logic and data <!-- .element: class="fragment" -->
- You can specify the behavior of your app before even starting to write the UI.
3. Scalable <!-- .element: class="fragment" -->
- Complexity through composition
</script>
</section>
<section data-markdown>
<script type="text/template">
More reasons:
- Smart people (including the creators of Flux) think it's the right direction
- Intuitive and decoupled
- Benefits of pure functional programming (easy to test, "time traveling debuggers", reproducible sessions, etc)
- This isn't new, the paradigm has been around for over 40 years
- Simple, only 2kb.
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## Using Redux with React
- Use redux-react helper to facilitation binding <!-- .element: class="fragment" -->
- Recommend passing relevant nodes of state into "smart" root-components, that pass props down to "dumb" middle/leaf components <!-- .element: class="fragment" -->
- UI hierarchy matches state hierarchy <!-- .element: class="fragment" -->
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## What about async?
</script>
</section>
<section data-markdown>
<script type="text/template">
## Middleware
Chainable dispatch plug-ins allowing you to inject behavior between receiving and action and processing it.
A useful place for side-effects - like logging... or making async requests!
</script>
</section>
<section data-markdown>
<script type="text/template">
Async flow:
- User-generated action pass into your middleware
- Your middleware detects a server request is necessary
- It fires off the async request and sets a "fetching" flag in the store
- The view updates to the fetching flag by showing a spinner
When the ajax request returns:
- The response generates a new action with the new data
- The store gets updated and the fetching flag is turned off
- The views can render the data
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## Links / resources
- Great docs - http://rackt.github.io/redux/
- Awesome redux - https://github.com/xgrommx/awesome-redux
</script>
</section>
</section>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
// Full list of configuration options available at:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
transition: 'slide', // none/fade/slide/convex/concave/zoom
// Optional reveal.js plugins
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/highlight/highlight.js', async: true, condition: function() { return !!document.querySelector( 'pre code' ); }, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true },
{ src: 'plugin/notes/notes.js', async: true }
]
});
</script>
</body>
</html>