malarkey

When times get tough and people get nasty, you’ll need more than a killer smile. You’ll need a killer contract.

Used by 1000s of designers and developers Clarify what’s expected on both sides Helps build great relationships between you and your clients Plain and simple, no legal jargon Customisable to suit your business Used on countless web projects since 2008

…………………………

CHH

<?php

function iterator_map(callable $callback)
{
    $iterators = array_slice(func_get_args(), 1);

    $multi = new MultipleIterator;
    foreach ($iterators as $it) {
        $multi->attachIterator($it);
    }

dbu

# -*- mode: ruby -*-
# vi: set ft=ruby :

this_dir = File.dirname(__FILE__) + "/"
require this_dir + "vagrant/hostmaster.rb"

Vagrant::Config.run do |config|

  # define some colors for our output
  def colorize(text, color_code) "#{color_code}#{text}\033[0m" end

jamierumbelow

{
    "require": {
        "phpunit/phpunit": "3.7.*"
    }
}

cheeaun

JSCamp.Asia 2012 Links & Resources

Web Site: http://jscamp.asia/ Twitter: http://twitter.com/jscamp_asia

Ping me @cheeaun on Twitter if you found some awesome stuff for #jscamp. This gist will be updated whenever there's new stuff.

Slides

getify

JavaScript does not have "inheritance" or "prototypal inheritance" or "classes" or any of that jazz... what you've been told, and how you've been taught about it, are a misunderstanding... all this nonsense about constructor functions and new and such... that's all hogwash... well, it's all unnecessary effort, at best.

"Instead... only try to realize the truth... there is no spoon."

What JavaScript does have is "behavior delegation"... and object linking through the "prototype chain"... you merely link two instances of objects together, say Foo and Baz, and say that Baz "delegates" to Foo for any behavior that Baz doesn't own itself but that Foo does own. And thus, any object b (aka, "b is an instance of Baz" in the more confusing terminology) which is linked to Baz, delegates first to Baz, and then to Foo, for behavior.

That's it. Seriously. And function constructors and new and all that stuff, everything you've read before about OO in JS, they're just distractions that lea

dhrrgn

<?php

$connection = Illuminate\Database\Connectors\ConnectionFactory::make([
    'driver'   => 'mysql',
    'host'     => '',
    'database' => '',
    'username' => '',
    'password' => '',
    'charset'  => '',
    'prefix'   => '',

dhrrgn

<?php
use Illuminate\Database\Connectors\ConnectionFactory;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Database\ConnectionResolver;
use Illuminate\Database\DatabaseManager;

class Db {

    private static $resolver = null;

Warry

How to make faster scroll effects?

• Avoid too many reflows (the browser to recalculate everything)
• Use advanced CSS3 for graphic card rendering
• Precalculate sizes and positions

Beware of reflows

The reflow appens as many times as there are frames per seconds. It recalculate all positions that change in order to diplay them. Basically, when you scroll you execute a function where you move things between two reflows. But there are functions that triggers reflows such as jQuery offset, scroll... So there are two things to take care about when you dynamically change objects in javascript to avoid too many reflows:

igorw

#!/bin/bash
# Amazing static site generator
# Works for PHP and HTML sites
# Assumes web root to be in /web
# Dumps the site into a directory named "static"

PORT=9999

php -S localhost:$PORT -t web >/dev/null &
PID=$!