-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathatom.xml
More file actions
5441 lines (4497 loc) · 425 KB
/
Copy pathatom.xml
File metadata and controls
5441 lines (4497 loc) · 425 KB
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
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title><![CDATA[4waisenkinder]]></title>
<link href="http://4waisenkinder.github.io/atom.xml" rel="self"/>
<link href="http://4waisenkinder.github.io/"/>
<updated>2015-01-03T18:24:07+01:00</updated>
<id>http://4waisenkinder.github.io/</id>
<author>
<name><![CDATA[Stefan Judis, Patrick Venetz, André Kussmann, Bernhard Weisshuhn]]></name>
</author>
<generator uri="http://octopress.org/">Octopress</generator>
<entry>
<title type="html"><![CDATA[How to react to changing environments using matchMedia]]></title>
<link href="http://4waisenkinder.github.io/blog/2014/12/26/handle-environment-changes-via-window-dot-matchmedia/"/>
<updated>2014-12-26T23:03:00+01:00</updated>
<id>http://4waisenkinder.github.io/blog/2014/12/26/handle-environment-changes-via-window-dot-matchmedia</id>
<content type="html"><![CDATA[<p>I was at my parents place over Christmas. Besides eating the whole day and playing board games I tried to read two books I brought with me.</p>
<p>One of the books was <a href="http://www.abookapart.com/products/responsible-responsive-design">RESPONSIBLE RESPONSIVE DESIGN</a> by <a href="https://twitter.com/scottjehl">Scott Jehl</a>. It was released recently and it is a really good read. I have not finished it yet, but I enjoy it and it is for sure in the TOP5 list of my favourite books about responsive web design.</p>
<!-- more -->
<p>In the world of responsive web design we deal with media queries all the time to give our visitors the best experience possible depending on the their devices and environments. Usually this means that web developers deal with screen dimensions inside of media queries and this is becoming crazier and more useful every day.</p>
<p>If you are interested in what may come in the future the spec for <a href="http://dev.w3.org/csswg/mediaqueries4">Media Queries Level 4</a> is quite interesting – check out the spec for <a href="http://dev.w3.org/csswg/mediaqueries4/#light-level">light-level</a>. ;)</p>
<p>Media queries are mostly used inside of the CSS files to adapt the styling to the particular device the visitor is using. This makes total sense, but responsive web design should not be only about “making it look pretty”.</p>
<h4>It should also be about only using and initializing needed components.</h4>
<p>At my last job I was working with <a href="http://foundation.zurb.com/">Foundation</a> a lot. And I really loved it. The <a href="http://foundation.zurb.com/docs/components/block_grid.html">block grid</a> is awesome! And also the <a href="http://foundation.zurb.com/docs/components/offcanvas.html">Off-canvas implementation</a> is quite nice in my opinion.</p>
<p>The only thing that always bothered me about the implementations in famous frameworks like <a href="http://getbootstrap.com/">Bootstrap</a> and <a href="http://foundation.zurb.com/">Foundation</a> is that the scripts and modules used for smaller devices are also executed on larger devices and vice versa.</p>
<p>No matter if the modules and their functionality are needed or not, the given code is executed and all event handlers are still bound. These event handlers will not be triggered in a lot of cases, because the given DOM elements connected to the functionality are hidden via CSS in several environment combinations.</p>
<p>When having a look at navigation solutions for smaller devices in both projects you will see that the JavaScript modules to guarantee a good experience on smaller devices are initialized and event handlers are bound for no reason – regardless of whether they are needed. This is a simple waste of CPU and not needed at all.</p>
<p><img class="center" src="http://4waisenkinder.github.io/images/blog/stefanjudis/mobileNavigationOnDesktop.jpg" width="600" height="324" title="Mobile event handlers still bound on larger devices" alt="Mobile event handlers still bound on larger devices"></p>
<p>There is a lot of discussion regarding what to serve to a customer in terms of feature detection and custom builds, but not every project has enough time and resources to implement complicated build systems.</p>
<p>This is why I started to initialize given modules only when needed. A custom build of <a href="http://modernizr.com/">Modernizr</a> is usually included in my projects so that the handy <code>Modernizr.mq</code> function is largely used to not initialize things that are not needed at all.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
</pre></td><td class='code'><pre><code class='javascript'><span class='line'><span class="c1">// only initialize the off-canvas </span>
</span><span class='line'><span class="c1">// navigation for smaller devices</span>
</span><span class='line'><span class="k">if</span> <span class="p">(</span> <span class="nx">Modernizr</span><span class="p">.</span><span class="nx">mq</span><span class="p">(</span> <span class="s1">'(max-width: 50em)'</span> <span class="p">)</span> <span class="p">)</span> <span class="p">{</span>
</span><span class='line'> <span class="c1">// initialize Foundation's offcanvas</span>
</span><span class='line'> <span class="nx">$document</span><span class="p">.</span><span class="nx">foundation</span><span class="p">(</span> <span class="s1">'offcanvas'</span> <span class="p">);</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<h3><code>Modernizr.mq</code> – how does it work?</h3>
<p>Let us have a look at how this function works. The functionality is defined in <a href="https://github.com/Modernizr/Modernizr/blob/master/src/mq.js">mq.js</a> and <a href="https://github.com/Modernizr/Modernizr/blob/master/src/testMediaQuery.js">testMediaQuery.js</a>.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
<span class='line-number'>19</span>
<span class='line-number'>20</span>
<span class='line-number'>21</span>
<span class='line-number'>22</span>
<span class='line-number'>23</span>
<span class='line-number'>24</span>
<span class='line-number'>25</span>
<span class='line-number'>26</span>
<span class='line-number'>27</span>
<span class='line-number'>28</span>
<span class='line-number'>29</span>
</pre></td><td class='code'><pre><code class='javascript'><span class='line'><span class="c1">// -> testMediaQuery.js</span>
</span><span class='line'><span class="nx">define</span><span class="p">([</span><span class="s1">'injectElementWithStyles'</span><span class="p">],</span> <span class="kd">function</span><span class="p">(</span> <span class="nx">injectElementWithStyles</span> <span class="p">)</span> <span class="p">{</span>
</span><span class='line'> <span class="c1">// adapted from matchMedia polyfill</span>
</span><span class='line'> <span class="c1">// by Scott Jehl and Paul Irish</span>
</span><span class='line'> <span class="c1">// gist.github.com/786768</span>
</span><span class='line'> <span class="kd">var</span> <span class="nx">testMediaQuery</span> <span class="o">=</span> <span class="p">(</span><span class="kd">function</span> <span class="p">()</span> <span class="p">{</span>
</span><span class='line'> <span class="kd">var</span> <span class="nx">matchMedia</span> <span class="o">=</span> <span class="nb">window</span><span class="p">.</span><span class="nx">matchMedia</span> <span class="o">||</span> <span class="nb">window</span><span class="p">.</span><span class="nx">msMatchMedia</span><span class="p">;</span>
</span><span class='line'> <span class="k">if</span> <span class="p">(</span> <span class="nx">matchMedia</span> <span class="p">)</span> <span class="p">{</span>
</span><span class='line'> <span class="k">return</span> <span class="kd">function</span> <span class="p">(</span> <span class="nx">mq</span> <span class="p">)</span> <span class="p">{</span>
</span><span class='line'> <span class="kd">var</span> <span class="nx">mql</span> <span class="o">=</span> <span class="nx">matchMedia</span><span class="p">(</span><span class="nx">mq</span><span class="p">);</span>
</span><span class='line'> <span class="k">return</span> <span class="nx">mql</span> <span class="o">&&</span> <span class="nx">mql</span><span class="p">.</span><span class="nx">matches</span> <span class="o">||</span> <span class="kc">false</span><span class="p">;</span>
</span><span class='line'> <span class="p">};</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'>
</span><span class='line'> <span class="k">return</span> <span class="kd">function</span> <span class="p">(</span> <span class="nx">mq</span> <span class="p">)</span> <span class="p">{</span>
</span><span class='line'> <span class="kd">var</span> <span class="nx">bool</span> <span class="o">=</span> <span class="kc">false</span><span class="p">;</span>
</span><span class='line'>
</span><span class='line'> <span class="nx">injectElementWithStyles</span><span class="p">(</span><span class="s1">'@media '</span> <span class="o">+</span> <span class="nx">mq</span> <span class="o">+</span> <span class="s1">' { #modernizr { position: absolute; } }'</span><span class="p">,</span> <span class="kd">function</span><span class="p">(</span> <span class="nx">node</span> <span class="p">)</span> <span class="p">{</span>
</span><span class='line'> <span class="nx">bool</span> <span class="o">=</span> <span class="p">(</span><span class="nb">window</span><span class="p">.</span><span class="nx">getComputedStyle</span> <span class="o">?</span>
</span><span class='line'> <span class="nb">window</span><span class="p">.</span><span class="nx">getComputedStyle</span><span class="p">(</span><span class="nx">node</span><span class="p">,</span> <span class="kc">null</span><span class="p">)</span> <span class="o">:</span>
</span><span class='line'> <span class="nx">node</span><span class="p">.</span><span class="nx">currentStyle</span><span class="p">)[</span><span class="s1">'position'</span><span class="p">]</span> <span class="o">==</span> <span class="s1">'absolute'</span><span class="p">;</span>
</span><span class='line'> <span class="p">});</span>
</span><span class='line'>
</span><span class='line'> <span class="k">return</span> <span class="nx">bool</span><span class="p">;</span>
</span><span class='line'> <span class="p">};</span>
</span><span class='line'> <span class="p">})();</span>
</span><span class='line'>
</span><span class='line'> <span class="k">return</span> <span class="nx">testMediaQuery</span><span class="p">;</span>
</span><span class='line'><span class="p">});</span>
</span></code></pre></td></tr></table></div></figure>
<p>As we see internally Modernizr uses the <code>matchMedia</code> function ( when available ), which is defined in the spec for the <a href="http://dev.w3.org/csswg/cssom-view">CSSOM View Module</a>. If <code>matchMedia</code> is not supported it provides a shim to achieve the same functionality.</p>
<h3><code>window.matchMedia</code> – so what?</h3>
<p><code>matchMedia</code> provides the functionality to check media queries on the JavaScript side. And the great thing about it is, that it is actual quite widely supported according to <a href="http://caniuse.com/#feat=matchmedia">caniuse.com</a>.</p>
<p><code>Modernizr.mq</code> already gives us support to get information on whether the given media query is matching or not. One key thing to watch out here is, that <code>matchMedia</code> does not return a boolean value to work with – instead it returns a <a href="http://dev.w3.org/csswg/cssom-view/#the-mediaquerylist-interface">MediaQueryList Interface</a>.</p>
<p>The information if the media query matches is stored inside of the property <code>matches</code>.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
</pre></td><td class='code'><pre><code class='javascript'><span class='line'><span class="p">(</span> <span class="kd">function</span><span class="p">(</span> <span class="nb">window</span><span class="p">,</span> <span class="nb">document</span> <span class="p">)</span> <span class="p">{</span>
</span><span class='line'> <span class="c1">// get MediaQueryList Interface</span>
</span><span class='line'> <span class="kd">var</span> <span class="nx">mql</span> <span class="o">=</span> <span class="nb">window</span><span class="p">.</span><span class="nx">matchMedia</span><span class="p">(</span> <span class="s1">'(min-width:20em)'</span> <span class="p">);</span>
</span><span class='line'> <span class="c1">// get a container to do something with it depending </span>
</span><span class='line'> <span class="c1">// on matching media query</span>
</span><span class='line'> <span class="kd">var</span> <span class="nx">container</span> <span class="o">=</span> <span class="nb">document</span><span class="p">.</span><span class="nx">getElementById</span><span class="p">(</span> <span class="s1">'container'</span> <span class="p">);</span>
</span><span class='line'> <span class="c1">// create new paragraph object</span>
</span><span class='line'> <span class="kd">var</span> <span class="nx">paragraph</span> <span class="o">=</span> <span class="nb">document</span><span class="p">.</span><span class="nx">createElement</span><span class="p">(</span> <span class="s1">'p'</span> <span class="p">);</span>
</span><span class='line'>
</span><span class='line'> <span class="c1">// set innerHTML depending on matching media query</span>
</span><span class='line'> <span class="nx">paragraph</span><span class="p">.</span><span class="nx">innerHTML</span> <span class="o">=</span> <span class="nx">mql</span><span class="p">.</span><span class="nx">matches</span> <span class="o">?</span>
</span><span class='line'> <span class="s1">'Yeah - matching!'</span> <span class="o">:</span>
</span><span class='line'> <span class="s1">'No - not matching!'</span><span class="p">;</span>
</span><span class='line'>
</span><span class='line'> <span class="c1">// append element to container</span>
</span><span class='line'> <span class="nx">container</span><span class="p">.</span><span class="nx">appendChild</span><span class="p">(</span> <span class="nx">paragraph</span> <span class="p">);</span>
</span><span class='line'><span class="p">}</span> <span class="p">)(</span> <span class="nb">window</span><span class="p">,</span> <span class="nb">document</span> <span class="p">);</span>
</span></code></pre></td></tr></table></div></figure>
<p>This is already great because this way we can easily evaluate if a particular JavaScript module needs to be initialized or not. But what about the case of changing environments like a changed viewport from portrait to landscape mode? This is something I have been struggling with for a while already – and while reading Scott Jehl’s book I just came across a super neat solution.</p>
<p>I already read a lot of articles about <code>matchMedia</code>, but I did not know before that it provides more than just the <code>matches</code> property.</p>
<p>The returned <code>MediaQueryList Interface</code> also provides the ability to attach listeners to the moment whenever the media query changes from matching to not matching or the other way around.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
<span class='line-number'>19</span>
<span class='line-number'>20</span>
<span class='line-number'>21</span>
<span class='line-number'>22</span>
<span class='line-number'>23</span>
<span class='line-number'>24</span>
<span class='line-number'>25</span>
<span class='line-number'>26</span>
<span class='line-number'>27</span>
<span class='line-number'>28</span>
<span class='line-number'>29</span>
<span class='line-number'>30</span>
<span class='line-number'>31</span>
<span class='line-number'>32</span>
</pre></td><td class='code'><pre><code class='javascript'><span class='line'><span class="p">(</span> <span class="kd">function</span><span class="p">(</span> <span class="nb">window</span><span class="p">,</span> <span class="nb">document</span> <span class="p">)</span> <span class="p">{</span>
</span><span class='line'> <span class="c1">// get MediaQueryList Interface</span>
</span><span class='line'> <span class="kd">var</span> <span class="nx">mql</span> <span class="o">=</span> <span class="nb">window</span><span class="p">.</span><span class="nx">matchMedia</span><span class="p">(</span> <span class="s1">'(min-width:20em)'</span> <span class="p">);</span>
</span><span class='line'> <span class="c1">// get a container to do something with it depending </span>
</span><span class='line'> <span class="c1">// on matching media query</span>
</span><span class='line'> <span class="kd">var</span> <span class="nx">container</span> <span class="o">=</span> <span class="nb">document</span><span class="p">.</span><span class="nx">getElementById</span><span class="p">(</span> <span class="s1">'container'</span> <span class="p">);</span>
</span><span class='line'> <span class="c1">// create new paragraph element</span>
</span><span class='line'> <span class="kd">var</span> <span class="nx">paragraph</span> <span class="o">=</span> <span class="nb">document</span><span class="p">.</span><span class="nx">createElement</span><span class="p">(</span> <span class="s1">'p'</span> <span class="p">);</span>
</span><span class='line'>
</span><span class='line'> <span class="c1">// set innerHTML depending on matching media query</span>
</span><span class='line'> <span class="nx">paragraph</span><span class="p">.</span><span class="nx">innerHTML</span> <span class="o">=</span> <span class="nx">mql</span><span class="p">.</span><span class="nx">matches</span> <span class="o">?</span>
</span><span class='line'> <span class="s1">'Yeah - matching!'</span> <span class="o">:</span>
</span><span class='line'> <span class="s1">'No - not matching!'</span><span class="p">;</span>
</span><span class='line'>
</span><span class='line'> <span class="c1">// append element to container</span>
</span><span class='line'> <span class="nx">container</span><span class="p">.</span><span class="nx">appendChild</span><span class="p">(</span> <span class="nx">paragraph</span> <span class="p">);</span>
</span><span class='line'>
</span><span class='line'> <span class="c1">// attach event listener to changed state</span>
</span><span class='line'> <span class="c1">// of the given media query</span>
</span><span class='line'> <span class="nx">mql</span><span class="p">.</span><span class="nx">addListener</span><span class="p">(</span> <span class="kd">function</span><span class="p">(</span> <span class="nx">mql</span> <span class="p">)</span> <span class="p">{</span>
</span><span class='line'> <span class="c1">// create new paragraph element</span>
</span><span class='line'> <span class="kd">var</span> <span class="nx">paragraph</span> <span class="o">=</span> <span class="nb">document</span><span class="p">.</span><span class="nx">createElement</span><span class="p">(</span> <span class="s1">'p'</span> <span class="p">);</span>
</span><span class='line'>
</span><span class='line'> <span class="c1">// set innerHTHML depending on matching media query</span>
</span><span class='line'> <span class="nx">paragraph</span><span class="p">.</span><span class="nx">innerHTML</span> <span class="o">=</span> <span class="nx">mql</span><span class="p">.</span><span class="nx">matches</span> <span class="o">?</span>
</span><span class='line'> <span class="s1">'Yeah - changed to matching!'</span> <span class="o">:</span>
</span><span class='line'> <span class="s1">'No - changed to not matching!'</span><span class="p">;</span>
</span><span class='line'>
</span><span class='line'> <span class="c1">// append element to container</span>
</span><span class='line'> <span class="nx">container</span><span class="p">.</span><span class="nx">appendChild</span><span class="p">(</span> <span class="nx">paragraph</span> <span class="p">);</span>
</span><span class='line'> <span class="p">}</span> <span class="p">);</span>
</span><span class='line'><span class="p">}</span> <span class="p">)(</span> <span class="nb">window</span><span class="p">,</span> <span class="nb">document</span> <span class="p">);</span>
</span></code></pre></td></tr></table></div></figure>
<p>This is exactly what I was looking for a while, it gives an easy way to enhance an interface on changing environments on the fly and save resources from the beginning.</p>
<p>If you want to play around with it I created a <a href="http://codepen.io/stefanjudis/pen/qEaxKR">pen</a> for you to play around with.</p>
<p>And this is it for today – I hope you enjoyed the short read. Any ideas and comments are more than welcome. :)</p>
<div class='octopress-authorbox'>
<div class="author-pic">
<img src="http://www.gravatar.com/avatar/22725c2d3eb331146549bf0d5d3c050c" alt="Stefan Judis" />
</div>
<div class="author-about">
<h3>Stefan Judis</h3>
<p>Frontend lover</p>
<ul class="author-links">
<li>
<a href="http://twitter.com/stefanjudis">@stefanjudis</a>
</li>
</ul>
</div>
</div>]]></content>
</entry>
<entry>
<title type="html"><![CDATA[NPM 2.0 and how it helps avoiding global dependencies]]></title>
<link href="http://4waisenkinder.github.io/blog/2014/10/18/npm-2-dot-0-and-the-much-better-star-npm-run-star-command/"/>
<updated>2014-10-18T20:50:00+02:00</updated>
<id>http://4waisenkinder.github.io/blog/2014/10/18/npm-2-dot-0-and-the-much-better-star-npm-run-star-command</id>
<content type="html"><![CDATA[<p>Today I was listening to the NodeUp <a href="http://nodeup.com/seventy">episode 70</a>, which is all about the <a href="https://www.npmjs.org/package/npm">npm command line client</a>. And there is tons of useful information in this episode. It is all about where npm is at the moment and what the plans are for the future. Especially the recent changes inside of the command line client are a heavy discussed topic and I highly recommend to listen to this episode, when you are dealing with <a href="https://www.npmjs.org/">npm</a> on a daily basis.</p>
<p>One thing that is mentioned and really gets me excited is the change regarding the functionality to run scripts via npm which was introduced in the latest major version of npm – <a href="http://blog.npmjs.org/post/98131109725/npm-2-0-0">npm@2.0.0</a>.<!-- more --></p>
<p>So let us reassess how to run scripts via npm, have a look at what has changed in version 2.0.0 and check why this is such a big deal.</p>
<h3>Running scripts via npm</h3>
<p>The configuration file for any project based on node and npm is the <code>package.json</code>. This file includes meta information like name, version and author of the depending project, but also defines all dependencies, which need to be installed via calling <code>npm install</code>. If you are not familiar with this file, there is an excellent <a href="http://browsenpm.org/package.json">interactive cheat sheet</a> out there and you may want to check it out.</p>
<p>One thing to notice is that you can also run scripts and execute commands via npm. To do so you can define an optional object as the <code>scripts</code> property inside of the <code>package.json</code> and define your wished commands. <a href="https://twitter.com/substack">@substack</a> wrote a <a href="http://substack.net/task_automation_with_npm_run">great article</a> about how to use this functionality extensively.</p>
<p>There is not much magic about this.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
</pre></td><td class='code'><pre><code class='json'><span class='line'><span class="p">{</span>
</span><span class='line'> <span class="nt">"name"</span><span class="p">:</span> <span class="s2">"blog-npm-run-scripts"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"version"</span><span class="p">:</span> <span class="s2">"1.0.0"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"description"</span><span class="p">:</span> <span class="s2">"Show of the new npm run command"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"scripts"</span><span class="p">:</span> <span class="p">{</span>
</span><span class='line'> <span class="nt">"echo"</span> <span class="p">:</span> <span class="s2">"echo \"Hello world\""</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<p>And then you can use <code>npm run</code> to kick it off – pretty straight forward.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'>> npm run <span class="nb">echo</span>
</span><span class='line'>
</span><span class='line'>> blog-npm-run-scripts@1.0.0 <span class="nb">echo</span> /Users/stefan/Sites/blog-npm-run-scripts
</span><span class='line'>> <span class="nb">echo</span> <span class="s2">"Hello world"</span>
</span><span class='line'>
</span><span class='line'>Hello world
</span></code></pre></td></tr></table></div></figure>
<p>This functionality had one downside so far. It was not able to pass arguments to the <code>npm run</code> command. And that is why you had to hardcode the arguments, which made the whole thing less flexible and harder to use. The only solution for having similar commands with different arguments was to define specific named scripts inside of the <code>package.json</code> including different arguments.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
</pre></td><td class='code'><pre><code class='json'><span class='line'><span class="p">{</span>
</span><span class='line'> <span class="nt">"name"</span><span class="p">:</span> <span class="s2">"blog-npm-run-scripts"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"version"</span><span class="p">:</span> <span class="s2">"1.0.0"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"description"</span><span class="p">:</span> <span class="s2">"Show of the new npm run command"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"scripts"</span><span class="p">:</span> <span class="p">{</span>
</span><span class='line'> <span class="nt">"echo_helloWorld"</span> <span class="p">:</span> <span class="s2">"echo \"Hello world\""</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"echo_foo"</span> <span class="p">:</span> <span class="s2">"echo \"Foo\""</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<h3>Passing arguments to <code>npm run</code></h3>
<p>Since version 2.0.0 it is now possible to pass arguments to the scripts defined in the <code>package.json</code>. And this is a big improvement on flexibility and makes the whole thing much more powerful. The <code>package.json</code> above including two scripts running the <code>echo</code> command can be combined into one and can accept the wished arguments.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
</pre></td><td class='code'><pre><code class='json'><span class='line'><span class="p">{</span>
</span><span class='line'> <span class="nt">"name"</span><span class="p">:</span> <span class="s2">"blog-npm-run-scripts"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"version"</span><span class="p">:</span> <span class="s2">"1.0.0"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"description"</span><span class="p">:</span> <span class="s2">"Show of the new npm run command"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"scripts"</span><span class="p">:</span> <span class="p">{</span>
</span><span class='line'> <span class="nt">"echo"</span> <span class="p">:</span> <span class="s2">"echo"</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<p>The syntax to pass arguments to the defined scripts is as follows. You have to use <code>npm run</code> and then devided by two dashes(<code>--</code>) you can pass any arguments you like to the command.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'>> npm run <span class="nb">echo</span> -- <span class="s2">"hello world"</span>
</span><span class='line'>
</span><span class='line'>> blog-npm-run-scripts@1.0.0 <span class="nb">echo</span> /Users/stefan/Sites/blog-npm-run-scripts
</span><span class='line'>> <span class="nb">echo</span> <span class="s2">"hello world"</span>
</span><span class='line'>
</span><span class='line'>hello world
</span></code></pre></td></tr></table></div></figure>
<h3>Setting up Grunt and gulp without the global dependency</h3>
<p>Using the <code>echo</code> command might not seem really useful, but we will come to a much more useful example now. I am doing mostly frontend development and that is why in almost every project that I work on either <a href="http://gruntjs.com/">Grunt</a> or <a href="http://gulpjs.com/">gulp</a> is included. Grunt and gulp are task runners, that come with huge plugin registries to help automate any task you can think of.</p>
<p>When you check the getting started guide of both projects you will find the instruction to install them globally.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'><span class="c"># install gulp globally</span>
</span><span class='line'><span class="nv">$ </span>npm install -g gulp
</span><span class='line'><span class="c"># install grunt globally</span>
</span><span class='line'><span class="nv">$ </span>npm install -g grunt-cli
</span></code></pre></td></tr></table></div></figure>
<p>This is absolutely fine when you are working alone and these tools are only supposed to be executed on your machine. But when you work together with other colleagues on a project or your process includes a <a href="http://www.martinfowler.com/articles/continuousIntegration.html">continuous integration</a> system, then every global dependency can be quite troublesome. It simply moves the entry barrier a bit higher and increases the complexity to get everything up and running.</p>
<p>So let us have a look how to avoid that. First step is to install the needed modules in our project and not globally anymore.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'><span class="c"># install gulp in the project</span>
</span><span class='line'><span class="nv">$ </span>npm install gulp
</span><span class='line'><span class="c"># install grunt in the project</span>
</span><span class='line'><span class="nv">$ </span>npm install grunt-cli
</span></code></pre></td></tr></table></div></figure>
<p>By calling <code>npm install</code> npm will install the module and depending, if it has the <a href="http://browsenpm.org/package.json#bin"><code>bin</code></a> property defined, it will create a <code>.bin</code> folder inside of the <code>node_modules</code> folder. This means that this folder will include all defined command line interfaces of your installed modules. In this case the <code>.bin</code> folder includes the binaries <code>gulp</code> and <code>grunt</code>.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'>node_modules
</span><span class='line'> |_ .bin
</span><span class='line'> |_ gulp
</span><span class='line'> |_ grunt
</span></code></pre></td></tr></table></div></figure>
<p>If you want to use either Grunt or gulp via the <code>npm run</code> command now, you can set them up inside of your <code>package.json</code>.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
</pre></td><td class='code'><pre><code class='json'><span class='line'><span class="p">{</span>
</span><span class='line'> <span class="nt">"name"</span><span class="p">:</span> <span class="s2">"blog-npm-run-scripts"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"version"</span><span class="p">:</span> <span class="s2">"1.0.0"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"description"</span><span class="p">:</span> <span class="s2">"Show of the new npm run command"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"scripts"</span><span class="p">:</span> <span class="p">{</span>
</span><span class='line'> <span class="nt">"gulp"</span> <span class="p">:</span> <span class="s2">"./node_modules/.bin/gulp"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"grunt"</span> <span class="p">:</span> <span class="s2">"./node_modules/.bin/grunt"</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<p>And then you can easily run your defined tasks with npm.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'><span class="c"># run 'dev' task with in project install grunt</span>
</span><span class='line'><span class="nv">$ </span>npm run grunt -- dev
</span><span class='line'><span class="c"># run 'dev' task with in project install gulp</span>
</span><span class='line'><span class="nv">$ </span>npm run gulp -- dev
</span></code></pre></td></tr></table></div></figure>
<p><strong>But wait, it comes even better!</strong></p>
<p>To make it a bit nicer npm provides a nifty feature, when setting up custom scripts. It puts <code>./node_modules/.bin</code> in the <code>PATH</code> environment, when it executes the script.</p>
<p>This means, we can make the <code>package.json</code> a bit cleaner.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
</pre></td><td class='code'><pre><code class='json'><span class='line'><span class="p">{</span>
</span><span class='line'> <span class="nt">"name"</span><span class="p">:</span> <span class="s2">"blog-npm-run-scripts"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"version"</span><span class="p">:</span> <span class="s2">"1.0.0"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"description"</span><span class="p">:</span> <span class="s2">"Show of the new npm run command"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"scripts"</span><span class="p">:</span> <span class="p">{</span>
</span><span class='line'> <span class="nt">"gulp"</span> <span class="p">:</span> <span class="s2">"gulp"</span><span class="p">,</span>
</span><span class='line'> <span class="nt">"grunt"</span> <span class="p">:</span> <span class="s2">"grunt"</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<p><strong>For me this is pure awesomeness!</strong></p>
<p>It means not only dropping a global dependency but rather simplifying the whole work and setup flow.</p>
<p>Getting everything up and running is not</p>
<ul>
<li>installing node (which will install npm also)</li>
<li>installing dependencies</li>
<li>installing global dependencies</li>
<li>and run e.g. Grunt</li>
</ul>
<p>anymore.</p>
<p>It becomes</p>
<ul>
<li>installing node</li>
<li>installing dependencies</li>
<li>and run everything via npm scripts</li>
</ul>
<p>only.</p>
<p>If you want to play around with this I set up an <a href="https://github.com/stefanjudis/npm2-run-scripts-tryout">example repository</a>, which includes Grunt and gulp ready to use without any global installation.</p>
<h3>Sum up</h3>
<p>For me it is clear, that I will drop any project required global dependency that can be installed via npm in the future, because having less global dependencies just means less troubles and quicker setup.</p>
<p>And that is it for now and if you have any comments or ideas on that, please let me know. I hope you enjoyed it. :)</p>
<div class='octopress-authorbox'>
<div class="author-pic">
<img src="http://www.gravatar.com/avatar/22725c2d3eb331146549bf0d5d3c050c" alt="Stefan Judis" />
</div>
<div class="author-about">
<h3>Stefan Judis</h3>
<p>Frontend lover</p>
<ul class="author-links">
<li>
<a href="http://twitter.com/stefanjudis">@stefanjudis</a>
</li>
</ul>
</div>
</div>]]></content>
</entry>
<entry>
<title type="html"><![CDATA[Control your CSS animations with *animation-fill-mode*]]></title>
<link href="http://4waisenkinder.github.io/blog/2014/10/13/control-your-css-animations-with-animation-fill-mode/"/>
<updated>2014-10-13T20:39:00+02:00</updated>
<id>http://4waisenkinder.github.io/blog/2014/10/13/control-your-css-animations-with-animation-fill-mode</id>
<content type="html"><![CDATA[<p>Recently I had some time to play around with some CSS animations. Unfortunately I am not able to use them on a regular basis in my daily work and that is why I am really enjoying to do <em>#cssonly</em> stuff in my free time.</p>
<p>When using CSS animation there are two different (not technical) types of css animation.<!-- more --> There are the animations that has a starting set of set CSS properties which is exactly the same as the properties set at the end of the animation. You can check the example below.</p>
<h3>Same start and end CSS properties</h3>
<pre class="codepen" data-height="400" data-type="result" data-href="ALJef" data-user="stefanjudis"><code> </code></pre>
<script async src="http://codepen.io:/assets/embed/ei.js"></script>
<p>The animation defines a movement of the red square by using <code>translate</code> and moves the square to the left, to the right and ends in the center where it actually started.</p>
<p><em>If you are not familiar with CSS animations you might want to read something about it on <a href="https://developer.mozilla.org/de/docs/Web/CSS/animation">MDN</a>.</em></p>
<h3>Different start and end CSS properties</h3>
<p>But then there is the other type of animations that do not have the same properties as the applied styles when they finish. And these animations were always something I was struggling with.</p>
<p>So let us change the animation for the red square, so that it only moves to the right and has a different styling as applied before the animation kickes in.</p>
<pre class="codepen" data-height="400" data-type="result" data-href="fElaA" data-user="stefanjudis"><code> </code></pre>
<script async src="http://codepen.io:/assets/embed/ei.js"></script>
<p>As you see the animation finishes and the square jumps back to its position defined by the CSS that is not part of the animation.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
</pre></td><td class='code'><pre><code class='css'><span class='line'><span class="nc">.square</span> <span class="p">{</span>
</span><span class='line'> <span class="o">//</span> <span class="n">some</span> <span class="n">more</span> <span class="n">stuff</span> <span class="n">here</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">name</span> <span class="o">:</span> <span class="n">move</span><span class="p">;</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">duration</span> <span class="o">:</span> <span class="m">1s</span><span class="p">;</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">iteration</span><span class="o">-</span><span class="n">count</span> <span class="o">:</span><span class="m">1</span><span class="p">;</span>
</span><span class='line'>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">0</span><span class="o">,</span> <span class="m">0</span> <span class="p">);</span>
</span><span class='line'><span class="p">}</span>
</span><span class='line'>
</span><span class='line'><span class="k">@keyframes</span> <span class="nt">move</span> <span class="p">{</span>
</span><span class='line'> <span class="nt">0</span><span class="o">%</span> <span class="p">{</span>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">0</span><span class="o">,</span> <span class="m">0</span> <span class="p">);</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="nt">100</span><span class="o">%</span> <span class="p">{</span>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">100</span><span class="o">%,</span> <span class="m">0</span> <span class="p">)</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<p>But, that is not what I wanted, I wanted the square to keep the properties defined in the last frame of the animation. So I googled a bit and landed on <a href="http://stackoverflow.com/questions/4359627/stopping-a-css3-animation-on-last-frame">stackoverflow</a>. The first answer you will find there, is to set up the base styling of the animated element to the end state of the animation.</p>
<pre class="codepen" data-height="400" data-type="result" data-href="GmCIf" data-user="stefanjudis"><code> </code></pre>
<script async src="http://codepen.io:/assets/embed/ei.js"></script>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
</pre></td><td class='code'><pre><code class='css'><span class='line'><span class="nc">.square</span> <span class="p">{</span>
</span><span class='line'> <span class="o">//</span> <span class="n">some</span> <span class="n">more</span> <span class="n">stuff</span> <span class="n">here</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">name</span> <span class="o">:</span> <span class="n">move</span><span class="p">;</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">duration</span> <span class="o">:</span> <span class="m">1s</span><span class="p">;</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">iteration</span><span class="o">-</span><span class="n">count</span> <span class="o">:</span><span class="m">1</span><span class="p">;</span>
</span><span class='line'>
</span><span class='line'> <span class="o">//</span> <span class="n">set</span> <span class="n">it</span> <span class="n">initially</span> <span class="n">to</span> <span class="n">the</span> <span class="n">state</span> <span class="n">of</span> <span class="n">the</span> <span class="n">animation</span> <span class="n">end</span>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">100</span><span class="o">%,</span> <span class="m">0</span> <span class="p">);</span>
</span><span class='line'><span class="p">}</span>
</span><span class='line'>
</span><span class='line'><span class="k">@keyframes</span> <span class="nt">move</span> <span class="p">{</span>
</span><span class='line'> <span class="nt">0</span><span class="o">%</span> <span class="p">{</span>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">0</span><span class="o">,</span> <span class="m">0</span> <span class="p">);</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="nt">100</span><span class="o">%</span> <span class="p">{</span>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">100</span><span class="o">%,</span> <span class="m">0</span> <span class="p">)</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<p>This works kind of well, but I never liked this way and it felt like it is not the correct solution. And it turned out quickly, that it actually is not. When I was playing around with animations I used <code>animation-delay</code> a lot. So let us check if the last solution is working in combination with the usage of <code>transition-delay</code>.</p>
<pre class="codepen" data-height="400" data-type="result" data-href="xHavI" data-user="stefanjudis"><code> </code></pre>
<script async src="http://codepen.io:/assets/embed/ei.js"></script>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
<span class='line-number'>19</span>
<span class='line-number'>20</span>
<span class='line-number'>21</span>
<span class='line-number'>22</span>
<span class='line-number'>23</span>
<span class='line-number'>24</span>
</pre></td><td class='code'><pre><code class='css'><span class='line'><span class="nc">.square</span> <span class="p">{</span>
</span><span class='line'> <span class="o">//</span> <span class="n">some</span> <span class="n">more</span> <span class="n">stuff</span> <span class="n">here</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">name</span> <span class="o">:</span> <span class="n">move</span><span class="p">;</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">duration</span> <span class="o">:</span> <span class="m">1s</span><span class="p">;</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">iteration</span><span class="o">-</span><span class="n">count</span> <span class="o">:</span><span class="m">1</span><span class="p">;</span>
</span><span class='line'>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">100</span><span class="o">%,</span> <span class="m">0</span> <span class="p">);</span>
</span><span class='line'>
</span><span class='line'> <span class="o">@</span><span class="n">for</span> <span class="err">$</span><span class="n">i</span> <span class="n">from</span> <span class="m">0</span> <span class="n">through</span> <span class="m">3</span> <span class="err">{</span>
</span><span class='line'> <span class="o">&:</span><span class="n">nth</span><span class="o">-</span><span class="n">child</span><span class="p">(</span><span class="err">#{$</span><span class="n">i</span> <span class="o">+</span> <span class="m">1</span><span class="p">}</span><span class="o">)</span> <span class="p">{</span>
</span><span class='line'> <span class="k">top</span> <span class="o">:</span> <span class="m">1</span> <span class="o">+</span> <span class="err">$</span><span class="n">i</span> <span class="o">*</span> <span class="m">6</span><span class="n">rem</span><span class="p">;</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">delay</span> <span class="o">:</span> <span class="err">#{$</span><span class="n">i</span><span class="p">}</span><span class="nt">s</span><span class="o">;</span>
</span><span class='line'> <span class="err">}</span>
</span><span class='line'> <span class="err">}</span>
</span><span class='line'><span class="err">}</span>
</span><span class='line'>
</span><span class='line'><span class="k">@keyframes</span> <span class="nt">move</span> <span class="p">{</span>
</span><span class='line'> <span class="nt">0</span><span class="o">%</span> <span class="p">{</span>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">0</span><span class="o">,</span> <span class="m">0</span> <span class="p">);</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="nt">100</span><span class="o">%</span> <span class="p">{</span>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">100</span><span class="o">%,</span> <span class="m">0</span> <span class="p">)</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<p>What I did was I implemented four elements, which have all the same animation but with different set <code>transition-delay</code> property. And as you see, the squares are not jumping back when the animation finishes, which is good, but they are jumping when the animation starts, because the base styling is matching the animation end.</p>
<p>That shows clearly, that setting the animation end styles to the elements you want to animate is not an option at all.</p>
<h3>animation-fill-mode for the rescue</h3>
<p>And basically there is a super easyIch komme solution to solve this problem (and I’m still surprised that it is not popping up, when googling this problem). There is the CSS property <a href="https://developer.mozilla.org/de/docs/Web/CSS/animation-fill-mode">animation-fill-mode</a>, which lets you define, if styles included in your defined animation should be applied to the depending element before and/or after the animation.</p>
<p>This means by applying <code>animation-fill-mode : forwards</code> to the animated squares, the squares can still have the base styling which should be applied before the animation starts and afterwards the styles defined in the animation at <code>100%</code> or <code>to</code> will be applied to the element when the animation finishes.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
<span class='line-number'>19</span>
<span class='line-number'>20</span>
<span class='line-number'>21</span>
<span class='line-number'>22</span>
<span class='line-number'>23</span>
<span class='line-number'>24</span>
<span class='line-number'>25</span>
</pre></td><td class='code'><pre><code class='css'><span class='line'><span class="nc">.square</span> <span class="p">{</span>
</span><span class='line'> <span class="o">//</span> <span class="n">some</span> <span class="n">more</span> <span class="n">stuff</span> <span class="n">here</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">name</span> <span class="o">:</span> <span class="n">move</span><span class="p">;</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">duration</span> <span class="o">:</span> <span class="m">1s</span><span class="p">;</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">iteration</span><span class="o">-</span><span class="n">count</span> <span class="o">:</span><span class="m">1</span><span class="p">;</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">fill</span><span class="o">-</span><span class="n">mode</span> <span class="o">:</span> <span class="n">forwards</span><span class="p">;</span>
</span><span class='line'>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">0</span><span class="o">,</span> <span class="m">0</span> <span class="p">);</span>
</span><span class='line'>
</span><span class='line'> <span class="o">@</span><span class="n">for</span> <span class="err">$</span><span class="n">i</span> <span class="n">from</span> <span class="m">0</span> <span class="n">through</span> <span class="m">3</span> <span class="err">{</span>
</span><span class='line'> <span class="o">&:</span><span class="n">nth</span><span class="o">-</span><span class="n">child</span><span class="p">(</span><span class="err">#{$</span><span class="n">i</span> <span class="o">+</span> <span class="m">1</span><span class="p">}</span><span class="o">)</span> <span class="p">{</span>
</span><span class='line'> <span class="k">top</span> <span class="o">:</span> <span class="m">1</span> <span class="o">+</span> <span class="err">$</span><span class="n">i</span> <span class="o">*</span> <span class="m">6</span><span class="n">rem</span><span class="p">;</span>
</span><span class='line'> <span class="n">animation</span><span class="o">-</span><span class="n">delay</span> <span class="o">:</span> <span class="err">#{$</span><span class="n">i</span><span class="p">}</span><span class="nt">s</span><span class="o">;</span>
</span><span class='line'> <span class="err">}</span>
</span><span class='line'> <span class="err">}</span>
</span><span class='line'><span class="err">}</span>
</span><span class='line'>
</span><span class='line'><span class="k">@keyframes</span> <span class="nt">move</span> <span class="p">{</span>
</span><span class='line'> <span class="nt">0</span><span class="o">%</span> <span class="p">{</span>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">0</span><span class="o">,</span> <span class="m">0</span> <span class="p">);</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'> <span class="nt">100</span><span class="o">%</span> <span class="p">{</span>
</span><span class='line'> <span class="n">transform</span> <span class="o">:</span> <span class="n">translate</span><span class="p">(</span> <span class="m">100</span><span class="o">%,</span> <span class="m">0</span> <span class="p">)</span>
</span><span class='line'> <span class="p">}</span>
</span><span class='line'><span class="p">}</span>
</span></code></pre></td></tr></table></div></figure>
<p>And here is the working result:</p>
<pre class="codepen" data-height="400" data-type="result" data-href="CtoyH" data-user="stefanjudis"><code> </code></pre>
<script async src="http://codepen.io:/assets/embed/ei.js"></script>
<p><strong>It can be as easy as that!</strong></p>
<p>And that is it for now – problem solved. :)</p>
<p>I thought it might be worth sharing and I hope you enjoyed it. And as always feedback is very welcome. :)</p>
<div class='octopress-authorbox'>
<div class="author-pic">
<img src="http://www.gravatar.com/avatar/22725c2d3eb331146549bf0d5d3c050c" alt="Stefan Judis" />
</div>
<div class="author-about">
<h3>Stefan Judis</h3>
<p>Frontend lover</p>
<ul class="author-links">
<li>
<a href="http://twitter.com/stefanjudis">@stefanjudis</a>
</li>
</ul>
</div>
</div>]]></content>
</entry>
<entry>
<title type="html"><![CDATA[Flatten your npm dependencies with dedupe]]></title>
<link href="http://4waisenkinder.github.io/blog/2014/06/09/flatten-your-dependencies-with-npm-dedupe/"/>
<updated>2014-06-09T21:52:00+02:00</updated>
<id>http://4waisenkinder.github.io/blog/2014/06/09/flatten-your-dependencies-with-npm-dedupe</id>
<content type="html"><![CDATA[<p>I use npm for a while now and it is heavily integrated in my daily workflow. One thing that always bothers me, is that a fresh <code>npm install</code> on your project will probably download the same packages over and over again. Let us imagine your project has multiple dependencies that all have one package defined as another dependency.<!-- more --></p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
</pre></td><td class='code'><pre><code class=''><span class='line'>a
</span><span class='line'>+-- b <-- depends on c@1.0.x
</span><span class='line'>| `-- c@1.0.10
</span><span class='line'>`-- d <-- depends on c@~1.0.9
</span><span class='line'> `-- c@1.0.10</span></code></pre></td></tr></table></div></figure>
<p>As you see above package <code>c</code> will be downloaded two times, although the dependencies <code>b</code> and <code>d</code> could use the same package. You might think now “So? Not a big deal…”, but depending on dependencies of your dependencies you end up with a much slower <code>npm install</code> process, because packages got downloaded multiple times. And if you deal with a big project with a lot of dependencies I am not talking about a few seconds. ;)</p>
<p>Additionally the installation process can become less stable. In my case I included the following dependencies in my <code>package.json</code>.</p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
</pre></td><td class='code'><pre><code class=''><span class='line'> "dependencies": {
</span><span class='line'> "grunt": "~0.4.5",
</span><span class='line'> "grunt-photobox": "~0.8.0",
</span><span class='line'> "grunt-phantomas": "~0.7.1"
</span><span class='line'> }</span></code></pre></td></tr></table></div></figure>
<p>The two grunt plugins either directly or one of their dependencies depend on <code>phantomjs</code>. This leads to the following output during the installation process.</p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
<span class='line-number'>10</span>
<span class='line-number'>11</span>
<span class='line-number'>12</span>
<span class='line-number'>13</span>
<span class='line-number'>14</span>
<span class='line-number'>15</span>
<span class='line-number'>16</span>
<span class='line-number'>17</span>
<span class='line-number'>18</span>
<span class='line-number'>19</span>
</pre></td><td class='code'><pre><code class=''><span class='line'>> phantomjs@1.9.7-8 install /Users/stefan/Sites/blog-npm-dedupe/node_modules/grunt-contrib-jasmine/node_modules/grunt-lib-phantomjs/node_modules/phantomjs
</span><span class='line'>> node install.js
</span><span class='line'>
</span><span class='line'>PhantomJS detected, but wrong version 1.9.2 @ /opt/local/bin/phantomjs.
</span><span class='line'>Download already available at /var/folders/03/cgg2bwfd6j92tfllylt5b91m0000gn/T/phantomjs/phantomjs-1.9.7-macosx.zip
</span><span class='line'>Extracting zip contents
</span><span class='line'>Copying extracted folder /var/folders/03/cgg2bwfd6j92tfllylt5b91m0000gn/T/phantomjs/phantomjs-1.9.7-macosx.zip-extract-1402344467586/phantomjs-1.9.7-macosx -> /Users/stefan/Sites/blog-npm-dedupe/node_modules/grunt-contrib-jasmine/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/phantom
</span><span class='line'>Writing location.js file
</span><span class='line'>Done. Phantomjs binary available at /Users/stefan/Sites/blog-npm-dedupe/node_modules/grunt-contrib-jasmine/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/phantom/bin/phantomjs
</span><span class='line'>
</span><span class='line'>> phantomjs@1.9.7-8 install /Users/stefan/Sites/blog-npm-dedupe/node_modules/grunt-phantomas/node_modules/phantomas/node_modules/phantomjs
</span><span class='line'>> node install.js
</span><span class='line'>
</span><span class='line'>PhantomJS detected, but wrong version 1.9.2 @ /opt/local/bin/phantomjs.
</span><span class='line'>Download already available at /var/folders/03/cgg2bwfd6j92tfllylt5b91m0000gn/T/phantomjs/phantomjs-1.9.7-macosx.zip
</span><span class='line'>Extracting zip contents
</span><span class='line'>Copying extracted folder /var/folders/03/cgg2bwfd6j92tfllylt5b91m0000gn/T/phantomjs/phantomjs-1.9.7-macosx.zip-extract-1402344475151/phantomjs-1.9.7-macosx -> /Users/stefan/Sites/blog-npm-dedupe/node_modules/grunt-phantomas/node_modules/phantomas/node_modules/phantomjs/lib/phantom
</span><span class='line'>Writing location.js file
</span><span class='line'>Done. Phantomjs binary available at /Users/stefan/Sites/blog-npm-dedupe/node_modules/grunt-phantomas/node_modules/phantomas/node_modules/phantomjs/lib/phantom/bin/phantomjs</span></code></pre></td></tr></table></div></figure>
<p>Two times the same package is downloaded and unfortunately the <code>phantomjs</code> package downloads <code>phantomjs</code> via npm script functionality. It downloads and unzipps data itself. In my case I had to fight against an unstable network, which led to a bunch of failing intallation processes. Sometimes the first <code>phantomjs</code> download did not work. Sometimes the second. And all the time <code>npm install</code> failed. Especially <code>phantomjs</code> is a really popular dependency and I am sure a lot of projects download it much more often than only two times. ;)</p>
<p>After this experience I started digging around a bit and discovered <code>npm dedupe</code> – docs are <a href="https://www.npmjs.org/doc/cli/npm-dedupe.html">here</a>. It will check your installed dependencies and finally flatten the dependency structure by moving shared packages higher in the tree. Less duplicated packages – yay!!!</p>
<p>To show the difference – the old structure was:</p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
</pre></td><td class='code'><pre><code class=''><span class='line'>grunt-phantomas
</span><span class='line'>`-- phantomas
</span><span class='line'> `-- phantomjs
</span><span class='line'>
</span><span class='line'>grunt-photobox
</span><span class='line'>`-- phantomjs</span></code></pre></td></tr></table></div></figure>
<p>And after using <code>dedupe</code> I ended up with:</p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
<span class='line-number'>9</span>
</pre></td><td class='code'><pre><code class=''><span class='line'>phantomjs
</span><span class='line'>
</span><span class='line'>// a lot of other shared
</span><span class='line'>// dependencies also here :)
</span><span class='line'>
</span><span class='line'>grunt-phantomas
</span><span class='line'>`-- phantomas
</span><span class='line'>
</span><span class='line'>grunt-photobox</span></code></pre></td></tr></table></div></figure>
<p>Super nice!</p>
<p>To make sure all your colleagues receive the same flattened dependency structure use <code>npm shrinkwrap</code> to really lock all packages including versions and hierarchy. In case you have not used <code>shrinkwrap</code> before I also wrote a <a href="http://4waisenkinder.de/blog/2013/07/10/why-you-should-use-npm-shrinkwrap-and-how-to-deal-with-a-dependency-fu-star-star-up/">post</a> about it.</p>
<p>To sum up, my workflow was the following:</p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
</pre></td><td class='code'><pre><code class=''><span class='line'>$ npm install
</span><span class='line'>
</span><span class='line'>$ npm dedupe
</span><span class='line'>
</span><span class='line'>$ npm shrinkwrap</span></code></pre></td></tr></table></div></figure>
<p><code>dedupe</code> is currently marked as experimental and unfortunately I made the experience, that it is not 100% stable at the moment. I filed already an issue <a href="https://github.com/npm/npm/issues/5448">here</a>. But we should really start using it, because it will make the installation of npm packages just quicker and safer. I am really looking forward to this feature and I am sure, that it will become stable soon.</p>
<p>Thanks for reading and all comments on this topic are as usual more than welcome. ;)</p>
<div class='octopress-authorbox'>
<div class="author-pic">
<img src="http://www.gravatar.com/avatar/22725c2d3eb331146549bf0d5d3c050c" alt="Stefan Judis" />
</div>
<div class="author-about">
<h3>Stefan Judis</h3>
<p>Frontend lover</p>
<ul class="author-links">
<li>
<a href="http://twitter.com/stefanjudis">@stefanjudis</a>
</li>
</ul>
</div>
</div>]]></content>
</entry>
<entry>
<title type="html"><![CDATA[Using basic and tween transitions in d3.js]]></title>
<link href="http://4waisenkinder.github.io/blog/2014/05/11/d3-dot-js-tween-in-detail/"/>
<updated>2014-05-11T13:25:00+02:00</updated>
<id>http://4waisenkinder.github.io/blog/2014/05/11/d3-dot-js-tween-in-detail</id>
<content type="html"><![CDATA[<p>Playing around at <a href="http://codepen.io">CodePen</a> is one of my favourite activities, when doing ‘nothing’ lately. Especially the combination of <a href="http://dribbble.com">dribbble</a> and CodePen is super nice. Browsing for beautiful designs and ideas on dribbble and putting them into code became a nice activity for me. There are a lot of great people hanging around at dribbble and you can get a lot of inspiration over there.</p>
<p>Over the last few month I started being interested in dashboards and how to analyze/visualize data. Unfortunately I am not a designer and this is why I really enjoy to just build dashboards according to a dribbble design.</p>