-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
564 lines (432 loc) · 22 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
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=1024" />
<meta name="apple-mobile-web-app-capable" content="yes" />
<title>Mid-sized javascript application - Barcamp 2012</title>
<meta name="description" content="impress.js is a presentation tool based on the power of CSS3 transforms and transitions in modern browsers and inspired by the idea behind prezi.com." />
<meta name="author" content="Bartek Szopka" />
<link href="http://fonts.googleapis.com/css?family=Open+Sans:regular,semibold,italic,italicsemibold|PT+Sans:400,700,400italic,700italic|PT+Serif:400,700,400italic,700italic" rel="stylesheet" />
<!--
Impress.js doesn't depend on any external stylesheet. Script adds all styles it needs for
presentation to work.
This style below contains styles only for demo presentation. Browse it to see how impress.js
classes are used to style presentation steps, or how to apply fallback styles, but I don't want
you to use them directly in your presentation.
Be creative, build your own. We don't really want all impress.js presentations to look the same,
do we?
When creating your own presentation get rid of this file. Start from scratch, it's fun!
-->
<link href="css/impress-demo.css" rel="stylesheet" />
<link href="css/style.css" rel="stylesheet" />
<link rel="shortcut icon" href="favicon.png" />
<link rel="apple-touch-icon" href="apple-touch-icon.png" />
</head>
<!--
Body element is used by impress.js to set some useful class names, that will allow you to detect
the support and state of the presentation in CSS or other scripts.
First very useful class name is `impress-not-supported`. This class means, that browser doesn't
support features required by impress.js, so you should apply some fallback styles in your CSS.
It's not necessary to add it manually on this element. If the script detects that browser is not
good enough it will add this class, but keeping it in HTML means that users without JavaScript
will also get fallback styles.
When impress.js script detects that browser supports all required features, this class name will
be removed.
The class name on body element also depends on currently active presentation step. More details about
it can be found later, when `hint` element is being described.
-->
<body class="impress-not-supported">
<!--
For example this fallback message is only visible when there is `impress-not-supported` class on body.
-->
<div class="fallback-message">
<p>Your browser <b>doesn't support the features required</b> by impress.js, so you are presented with a simplified version of this presentation.</p>
<p>For the best experience please use the latest <b>Chrome</b>, <b>Safari</b> or <b>Firefox</b> browser.</p>
</div>
<!--
Now that's the core element used by impress.js.
That's the wrapper for your presentation steps. In this element all the impress.js magic happens.
It doesn't have to be a `<div>`. Only `id` is important here as that's how the script find it.
You probably won't need it now, but there are some configuration options that can be set on this element.
To change the duration of the transition between slides use `data-transition-duration="2000"` giving it
a number of ms. It defaults to 1000 (1s).
You can also control the perspective with `data-perspective="500"` giving it a number of pixels.
It defaults to 1000. You can set it to 0 if you don't want any 3D effects.
If you are willing to change this value make sure you understand how CSS perspective works:
https://developer.mozilla.org/en/CSS/perspective
But as I said, you won't need it for now, so don't worry - there are some simple but interesing things
right around the corner of this tag ;)
-->
<div id="impress">
<!--
Here is where interesting thing start to happen.
Each step of the presentation should be an element inside the `#impress` with a class name
of `step`. These step elements are positioned, rotated and scaled by impress.js, and
the 'camera' shows them on each step of the presentation.
Positioning information is passed through data attributes.
In the example below we only specify x and y position of the step element with `data-x="-1000"`
and `data-y="-1500` attributes. This means that **the center** of the element (yes, the center)
will be positioned in point x = -1000px and y = -1500px of the presentation 'canvas'.
It will not be rotated or scaled.
-->
<div id="bored" class="step slide" data-x="-2000" data-y="-1500">
<h1>JS 201, when JS becomes hard to manage</h1>
<p>Joe Tsui</p>
<q>@<span class="red">joe</span><span class="orange">tsui</span><span class="blue">hk</span></q>
<p>JS, Drupal, Django</p>
</div>
<!--
The `id` attribute of the step element is used to identify it in the URL, but it's optional.
If it is not defined, it will get a default value of `step-N` where N is a number of slide.
So in the example below it'll be `step-2`.
The hash part of the url when this step is active will be `#/step-2`.
You can also use `#step-2` in a link, to point directly to this particular step.
Please note, that while `#/step-2` (with slash) would also work in a link it's not recommended.
Using classic `id`-based links like `#step-2` makes these links usable also in fallback mode.
-->
<div class="step slide" data-x="-1000" data-y="-1500">
<h1>NOT:</h1>
<ul>
<li>core/modules setup</li>
<li>js template language</li>
<li>a clear MVC/MCC pattern</li>
</ul>
<h1>BUT:</h1>
<ul>
<li>More than 5 js files to manage</li>
<li>Spaghetti code is no good</li>
</ul>
</div>
<div class="step slide" data-x="0" data-y="-1500">
<h1>Scoreboard</h1>
<q>a weekend(sss) project that track scores in turn based board games.</q>
</div>
<div class="step slide" data-x="1000" data-y="-1500">
<h1>Libraries used</h1>
<ul>
<li>JQuery</li>
<li>Twitter bootstrap</li>
<li>Google web font API</li>
<li>HTML5, CSS3</li>
<li>More..</li>
<ul>
</div>
<div class="step slide" data-x="2000" data-y="-1500">
<h1>Some kind of storage to cater page reload</h1>
<h3>Local storage</h3>
<p>Keep unless specified or clear cache</p>
<h3>Session storage</h3>
<p>Keep within session</p>
</div>
<div class="step slide" data-x="2000" data-y="-500">
<h1>API:</h1>
<h3>Set</h3>
<code>
<script src="https://gist.github.com/3104124.js?file=Set session storage API.js"></script>
</code>
<h3>Get</h3>
<code>
<script src="https://gist.github.com/3104124.js?file=Get session storage API.js"></script>
</code>
</div>
<div class="step slide" data-x="2000" data-y="500">
<h1>NoSQL</h1>
<h3>key value store</h3>
<p>[game_id]:[user_id]:score => 2</p>
<p>[game_id]:[user_id]:color => red</p>
<p>[game_id]:global:[user_list] => 1234,3456</p>
</div>
<div class="step slide" data-x="3000" data-y="-1500">
<h1>Audio</h1>
</div>
<div class="step slide" data-x="3000" data-y="-500">
<h1>Game Audio API sucks</h1>
<ul>
<li><a href="http://www.html5rocks.com/en/features/multimedia">html5rocks</a></li>
<li><a href="http://www.html5rocks.com/en/tutorials/webaudio/intro/">Getting started with web audio API</a></li>
<li><a href="http://www.html5rocks.com/en/tutorials/webaudio/games/">Developing game audio with the web audio API</a></li>
<li><a href="http://www.cuttherope.ie/dev/">Cut the rope</a></p>
</ul>
</div>
<div class="step slide" data-x="3000" data-y="500">
<h1>JUST PLAY A <span style="color:#f00;">#@%&ING</span> MIDI</h1>
</div>
<div class="step slide" data-x="4000" data-y="-1500">
<h1>Sync across device</h1>
</div>
<div class="step slide" data-x="4000" data-y="-500">
<h1>Real time</h1>
</div>
<div class="step slide" data-x="4000" data-y="500">
<h1>Web socket</h1>
<h3>Socket.io</h3>
</div>
<div class="step slide" data-x="4000" data-y="1500">
<h1>JS API</h1>
<h3>Uplink</h3>
<script src="https://gist.github.com/3104124.js?file=socket uplink.js"></script>
<h3>Downlink</h3>
<script src="https://gist.github.com/3104124.js?file=socket downlink.js"></script>
</div>
<div class="step slide" data-x="4000" data-y="2500">
<h1>Node.js API</h1>
<h3>Listen to events</h3>
<script src="https://gist.github.com/3104124.js?file=socket downlink.js"></script>
<h3>Broadcast (to other clients)</h3>
<script src="https://gist.github.com/3104124.js?file=broadcast.js"></script>
</div>
<div class="step slide" data-x="4000" data-y="3500">
<h1>Rooms</h1>
<script src="https://gist.github.com/3104124.js?file=join a room.js"></script>
</div>
<div class="step slide" data-x="5000" data-y="-1500">
<h1>Data on server side</h1>
</div>
<div class="step slide" data-x="5000" data-y="-500">
<h1>Redis</h1>
</div>
<div class="step slide" data-x="5000" data-y="500">
<h1>Redis</h1>
<ul>
<li>NoSQL</li>
<li>node.js</li>
<li>fast</li>
<li>fun, easy to use</li>
</ul>
<h3>Reuse session storage data schema</h3>
</div>
<div class="step slide" data-x="5000" data-y="1500">
<h1>Redis: Hash</h1>
<h3>HMSET [namespace] [key] [value] ...</h3>
<p>>HMSET user:1000 username joe password P1pp0</p>
<p>>HGETALL user:1000</p>
<p>username => joe</p>
<p>password => P1pp0</p>
</div>
<div class="step slide" data-x="5000" data-y="2500">
<h1>transparent mapping</h1>
<h3>[game_id]:[user_id]:score => 2</h3>
<h3>redis_client.hset([game_id]+':'+[user_id], score, 2);</h3>
</div>
<div class="step slide" data-x="6000" data-y="-1500">
<h1>Animations</h1>
</div>
<div class="step slide" data-x="6000" data-y="-500">
<h1>Out sourced most animations to CSS3</h1>
<q>jQuery do animations, even in CSS3 with plugins</q>
</div>
<div class="step slide" data-x="6000" data-y="500">
<h1>BUT</h1>
</div>
<div class="step slide" data-x="6000" data-y="1500">
<h1>Managing transitioning state is challenging</h1>
<h3>What to do when user clicks during a fade?</h3>
<p>Getting dirty hands there</p>
</div>
<div class="step slide" data-x="6000" data-y="2500">
<h1>Managing "state" added unintented complex</h1>
<h3>Moving, static, disappearing etc etc</h3>
</div>
<div class="step slide" data-x="7000" data-y="-1500">
<h1>Event based architecture</h1>
<h3>Custom events</h3>
</div>
<div class="step slide" data-x="7000" data-y="-500">
<h1>Events</h1>
<h3>User(s) add points</h3>
<h3>Ordering changed</h3>
<h3>New user</h3>
<h3>etc...</h3>
</div>
<div class="step slide" data-x="7000" data-y="500">
<h1>Throw a event</h1>
<h1>Catch it somewhere</h1>
</div>
<div class="step slide" data-x="7000" data-y="1500">
<q>trigger()</q>
<script src="https://gist.github.com/3104124.js?file=tigger.js"></script>
<q>on()</q>
<script src="https://gist.github.com/3104124.js?file=on.js"></script>
</div>
<div class="step slide" data-x="7000" data-y="2500">
<q>trigger()</q>
<script src="https://gist.github.com/3104124.js?file=user add score.js"></script>
<q>on()</q>
<script src="https://gist.github.com/3104124.js?file=user add score storage.js"></script>
</div>
<div class="step slide" data-x="7000" data-y="3500">
<h1>Effectively decoupling code into meaningful context/files</h1>
<h3>Apps better organised</h3>
<h3>Code become modular</h3>
<p>Code change in one place is less likely to affect others</p>
</div>
<div class="step slide" data-x="8000" data-y="-1500">
<h1>Mulitple event handler</h1>
</div>
<div class="step slide" data-x="8000" data-y="-500">
<q>trigger()</q>
<code>user.trigger('add-score', [score:1])</code>
<q>on()</q>
<code>user.on('add-score', 'add_score_storage'); //localstorage.js</code>
<br />
<code>user.on('add-score', 'add_score_broadcast'); //socket.js</code>
<br />
<code>user.on('add-score', 'add_score_sound'); //sound.js</code>
</div>
<div class="step slide" data-x="8000" data-y="500">
<h1>2+ on() listening to the same event</h1>
</div>
<div class="step slide" data-x="8000" data-y="1500">
<h1>Can work with modernizr</h1>
<h3>Event catchers are distributed to files<h3>
</div>
<div class="step slide" data-x="8000" data-y="2500">
<h1>Can use a more robust PubSub</h1>
<h3>DOM performance is not that great</h3>
</div>
<div class="step slide" data-x="9000" data-y="-1500">
<img id="application-stack" src="barcamp2012-summer.png" alt="Application stack" />
</div>
<div class="step slide" data-x="10000" data-y="-1500">
<h1>Credits</h1>
<ul>
<li>Powered by impress.js</li>
<li>Code highlighting by Gist</li>
</ul>
</div>
<div class="step slide" data-x="11000" data-y="-1500">
<h1>Thanks!</h1>
<h3>Joe Tsui (@joetsuihk)</h3>
</div>
<!--
This is an example of step element being scaled.
Again, we use a `data-` attribute, this time it's `data-scale="4"`, so it means that this
element will be 4 times larger than the others.
From presentation and transitions point of view it means, that it will have to be scaled
down (4 times) to make it back to it's correct size.
-->
<!--
This element introduces rotation.
Notation shouldn't be a surprise. We use `data-rotate="90"` attribute, meaning that this
element should be rotated by 90 degrees clockwise.
-->
<!--
And now it gets really exiting! We move into third dimension!
Along with `data-x` and `data-y`, you can define the position on third (Z) axis, with
`data-z`. In the example below we use `data-z="-3000"` meaning that element should be
positioned far away from us (by 3000px).
-->
<!--
This step here doesn't introduce anything new when it comes to data attributes, but you
should notice in the demo that some words of this text are being animated.
It's a very basic CSS transition that is applied to the elements when this step element is
reached.
At the very beginning of the presentation all step elements are given the class of `future`.
It means that they haven't been visited yet.
When the presentation moves to given step `future` is changed to `present` class name.
That's how animation on this step works - text moves when the step has `present` class.
Finally when the step is left the `present` class is removed from the element and `past`
class is added.
So basically every step element has one of three classes: `future`, `present` and `past`.
Only one current step has the `present` class.
-->
<!--
And the last one shows full power and flexibility of impress.js.
You can not only position element in 3D, but also rotate it around any axis.
So this one here will get rotated by -40 degrees (40 degrees anticlockwise) around X axis and
10 degrees (clockwise) around Y axis.
You can of course rotate it around Z axis with `data-rotate-z` - it has exactly the same effect
as `data-rotate` (these two are basically aliases).
-->
<!--
So to make a summary of all the possible attributes used to position presentation steps, we have:
* `data-x`, `data-y`, `data-z` - they define the position of **the center** of step element on
the canvas in pixels; their default value is 0;
* `data-rotate-x`, `data-rotate-y`, 'data-rotate-z`, `data-rotate` - they define the rotation of
the element around given axis in degrees; their default value is 0; `data-rotate` and `data-rotate-z`
are exactly the same;
* `data-scale` - defines the scale of step element; default value is 1
These values are used by impress.js in CSS transformation functions, so for more information consult
CSS transfrom docs: https://developer.mozilla.org/en/CSS/transform
-->
<div id="overview" class="step" data-x="4500" data-y="1000" data-scale="9">
</div>
</div>
<!--
Hint is not related to impress.js in any way.
But it can show you how to use impress.js features in creative way.
When the presentation step is shown (selected) its element gets the class of "active" and the body element
gets the class based on active step id `impress-on-ID` (where ID is the step's id)... It may not be
so clear because of all these "ids" in previous sentence, so for example when the first step (the one with
the id of `bored`) is active, body element gets a class of `impress-on-bored`.
This class is used by this hint below. Check CSS file to see how it's shown with delayed CSS animation when
the first step of presentation is visible for a couple of seconds.
...
And when it comes to this piece of JavaScript below ... kids, don't do this at home ;)
It's just a quick and dirty workaround to get different hint text for touch devices.
In a real world it should be at least placed in separate JS file ... and the touch content should be
probably just hidden somewhere in HTML - not hard-coded in the script.
Just sayin' ;)
-->
<script>
if ("ontouchstart" in document.documentElement) {
document.querySelector(".hint").innerHTML = "<p>Tap on the left or right to navigate</p>";
}
</script>
<!--
Last, but not least.
To make all described above really work, you need to include impress.js in the page.
I strongly encourage to minify it first.
In here I just include full source of the script to make it more readable.
You also need to call a `impress().init()` function to initialize impress.js presentation.
And you should do it in the end of your document. Not only because it's a good practice, but also
because it should be done when the whole document is ready.
Of course you can wrap it in any kind of "DOM ready" event, but I was too lazy to do so ;)
-->
<script src="js/impress.js"></script>
<script>impress().init();</script>
<!--
The `impress()` function also gives you access to the API that controls the presentation.
Just store the result of the call:
var api = impress();
and you will get three functions you can call:
`api.init()` - initializes the presentation,
`api.next()` - moves to next step of the presentation,
`api.prev()` - moves to previous step of the presentation,
`api.goto( idx | id | element, [duration] )` - moves the presentation to the step given by its index number
id or the DOM element; second parameter can be used to define duration of the transition in ms,
but it's optional - if not provided default transition duration for the presentation will be used.
You can also simply call `impress()` again to get the API, so `impress().next()` is also allowed.
Don't worry, it wont initialize the presentation again.
For some example uses of this API check the last part of the source of impress.js where the API
is used in event handlers.
-->
</body>
</html>
<!--
Now you know more or less everything you need to build your first impress.js presentation, but before
you start...
Oh, you've already cloned the code from GitHub?
You have it open in text editor?
Stop right there!
That's not how you create awesome presentations. This is only a code. Implementation of the idea that
first needs to grow in your mind.
So if you want to build great presentation take a pencil and piece of paper. And turn off the computer.
Sketch, draw and write. Brainstorm your ideas on a paper. Try to build a mind-map of what you'd like
to present. It will get you closer and closer to the layout you'll build later with impress.js.
Get back to the code only when you have your presentation ready on a paper. It doesn't make sense to do
it earlier, because you'll only waste your time fighting with positioning of useless points.
If you think I'm crazy, please put your hands on a book called "Presentation Zen". It's all about
creating awesome and engaging presentations.
Think about it. 'Cause impress.js may not help you, if you have nothing interesting to say.
-->
<!--
Are you still reading this?
For real?
I'm impressed! Feel free to let me know that you got that far (I'm @bartaz on Twitter), 'cause I'd like
to congratulate you personally :)
But you don't have to do it now. Take my advice and take some time off. Make yourself a cup of coffee, tea,
or anything you like to drink. And raise a glass for me ;)
Cheers!
-->