I say "animated gif" but in reality I think it's irresponsible to be serving "real" GIF files to people now. You should be serving gfy's, gifv's, webm, mp4s, whatever. They're a fraction of the filesize making it easier for you to deliver high fidelity, full color animation very quickly, especially on bad mobile connections. (But I suppose if you're just doing this for small audiences (like bug reporting), then LICEcap is a good solution).
| <script src="http://static.tumblr.com/fpifyru/VCxlv9xwi/writecapture.js"></script> | |
| <script type="text/javascript"> | |
| $(function() { | |
| $("a[href]").each( | |
| function(index, element) { | |
| if ( $(element).attr('href').indexOf('gist.github.com') > 0 ) { | |
| var divElement = $('<div></div>'); | |
| $(element).after(divElement); | |
| writeCapture.html(divElement, '<script src="'+$(element).attr('href')+'.js"></'+'script>'); |
| var c = function(n) { | |
| var string = ''; | |
| n = Math.floor(n * Math.pow(256, 3)); | |
| for (var i = 5; i >= 0; i--) { | |
| string += (Math.floor(n / Math.pow(16, i)) % 16).toString(16); | |
| } | |
| return '#' + string; | |
| } |
This contract for general design sevices is a hybrid of this one on Docracy and the AIGA one also found on Docracy. I wanted something that was simple yet covered the important bits such as payment schedule, kill fee, liability, rights etc. Change the parts in square brackets to suit. I've had this checked by a lawyer but I recommend if you decide to use it you also get it looked at by a lawyer too. Never do work without a contract in place. The majority of clients are good, decent and want to create great work with you — having a solid contract in place will strengthen that relationship and provide you with protection should things go awry.
Operator Mono w/ Italics on OSX Vim
git checkout master # you can avoid this line if you are in master...
git subtree split --prefix dist -b gh-pages # create a local gh-pages branch containing the splitted output folder
git push -f origin gh-pages:gh-pages # force the push of the gh-pages branch to the remote gh-pages branch at origin
git branch -D gh-pages # delete the local gh-pages because you will need it: ref
| { | |
| "caret_extra_bottom": 2, | |
| "caret_extra_top": 2, | |
| "caret_extra_width": 1, | |
| "caret_style": "phase", | |
| "color_scheme": "Packages/Base16 Color Schemes/Themes/base16-oceanicnext.tmTheme", | |
| "create_window_at_startup": false, | |
| "ensure_newline_at_eof_on_save": true, | |
| "fold_buttons": false, | |
| "folder_exclude_patterns": |
tl;dr I built a demo illustrating what it might look like to add async rendering to Facebook's commenting interface, while ensuring it appears on the screen simultaneous to the server-rendered story.
A key benefit of async rendering is that large updates don't block the main thread; instead, the work is spread out and performed during idle periods using cooperative scheduling.
But once you make something async, you introduce the possibility that things may appear on the screen at separate times. Especially when you're dealing with multiple UI frameworks, as is often the case at Facebook.
How do we solve this with React?
A list of useful commands for the FFmpeg command line tool.
Download FFmpeg: https://www.ffmpeg.org/download.html
Full documentation: https://www.ffmpeg.org/ffmpeg.html