| // Conway's Game of Life for HTML5 Canvas | |
| // By Simon Laroche | |
| var FPS = 5; | |
| var paused = true; | |
| var gameStarted = false; | |
| var gLoop; | |
| var generations = 0; | |
| var population = 0; |
This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.
| // -------------------------------------------------- | |
| // Flexbox LESS mixins | |
| // The spec: http://www.w3.org/TR/css3-flexbox | |
| // -------------------------------------------------- | |
| // Flexbox display | |
| // flex or inline-flex | |
| .flex-display(@display: flex) { | |
| display: ~"-webkit-@{display}"; | |
| display: ~"-ms-@{display}box"; // IE10 uses -ms-flexbox |
Couldn't find the text of this for a while...
The following document is a written account of the Code School screencasting framework. It should be used as a reference of the accompanying screencast on the topic.
You're probably aren't going to take the time to read this document if you're not interested, but there are a lot of nice side effects caused by learning how to create quality screencasts.
| /* | |
| Grep.js | |
| Author : Nic da Costa ( @nic_daCosta ) | |
| Created : 2012/11/14 | |
| Version : 0.2 | |
| (c) Nic da Costa | |
| License : MIT, GPL licenses | |
| Overview: | |
| Basic function that searches / filters any object or function and returns matched properties. |
Authored by Peter Rybin , Chrome DevTools team
In this short guide we'll review some new Chrome DevTools features for "function scope" and "internal properties" by exploring some base JavaScript language concepts.
Let's start with closures – one of the most famous things in JS. A closure is a function, that uses variables from outside. See an example:
| Released under Creative Commons license (http://creativecommons.org/licenses/by/2.0/uk/) | |
| Timestamp,Where are you based in the UK?,How would you describe what you do,Is your primary skill set ,How old are you?,How many years have you been a web professional?,What is your day (not hourly) rate?,Average,How many years have you been freelance?,How do you charge clients?,Do you normally require a deposit before starting work on a project?,Do you normally use a contract?,Do you primarily work …,What is the average value of projects you work on?,What is your gender? | |
| 7/26/2012 8:59:32,South East,Front-end Designer / Developer,Mixture of all three,15-19,0-1,240,240,2-3,By the hour,10-25% of project value,Yes,"directly with clients, in partnership with other freelancers, subcontracting for agencies",£1001-2000,Male | |
| 5/18/2012 10:04:17,East Midlands,"Graphic Design, Front End Developer",Design ,25-29,6-7,220,220,2-3,By the hour,10-25% of project value,Yes,"directly with clients, in partnership with other freelancers, su |
#Introduction
Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.
Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.
