kronda

#!/bin/bash

SELENIUM=/usr/local/bin/selenium-server.jar
LOG=/var/log/selenium.log
PIDFILE=/opt/bin/selenium.pid

ARG=$1

if [ ${#ARG} -lt 1 ]
    then echo "\nUSAGE: $0 {start|stop}\n"                                    

james2doyle

$provinces = array(0 => 'Alberta',
1 => 'British Columbia',
2 => 'Manitoba',
3 => 'New Brunswick',
4 => 'Newfoundland and Labrador',
5 => 'Northwest Territories',
6 => 'Nova Scotia',
7 => 'Nunavut',
8 => 'Ontario',
9 => 'Prince Edward Island',

SimonSimCity

{#
  Source: http://dev.dbl-a.com/symfony-2-0/symfony2-and-twig-pagination/
  Updated by: Simon Schick <[email protected]>

  Parameters:
    * currentFilters (array) : associative array that contains the current route-arguments
    * currentPage (int) : the current page you are in
    * paginationPath (string) : the route name to use for links
    * showAlwaysFirstAndLast (bool) : Always show first and last link (just disabled)
    * lastPage (int) : represents the total number of existing pages

egaumer

/*jshint globalstrict:true */
/*global angular:true */
'use strict';

angular.module('demo', [
    'demo.controllers',
    'demo.directives',
    'elasticjs.service'
]);

pwc3

tell application "Calendar"
    -- delete everything from the destination calendar
    -- TODO: Change "Destination Calendar" to be the name of your destination calendar
    repeat with anEvent in (get events of calendar "Destination Calendar")
        delete anEvent
    end repeat
    
    -- copy all events from the source calendar to the destination
    -- TODO: Change "Source Calendar" to be the name of your source calendar
    -- TODO: Change "Destination Calendar" to be the name of your destination calendar

mjsuhonos

{
    "@context": {
        "ladder": "Ladder:",
        "bibo": "http://purl.org/ontology/bibo/",
        "dcterms": "http://purl.org/dc/terms/",
        "foaf": "http://xmlns.com/foaf/0.1/",
        "mads": "http://www.loc.gov/mads/rdf/v1#",
        "mods": "http://www.loc.gov/mods/modsrdf/v1#",
        "schema": "http://schema.org/",
        "skos": "http://www.w3.org/2004/02/skos/core#"

torgeir

window.AudioContext = window.AudioContext || window.webkitAudioContext;
navigator.getUserMedia = navigator.getUserMedia || navigator.webkitGetUserMedia;

window.addEventListener('load', init, false);

function init () {
  try {
    record(new AudioContext());
  }
  catch (e) {

elidupuis

Dependencies managed with Bower:

npm install -g bower
bower install

...Then open up index.html in a browser.

impressiver

/******************************************************************************
 *
 * Adapter functions to deal w/ Angular <--> jQuery (custom) events
 * 
 * I wrote these quickly just to see if they'd fly. They should really be added
 * to a provider, I just haven't gotten around it.
 *
 *****************************************************************************/

/**

xjamundx

This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.

In that post I talked about 3 main reasons for moving from require.js to webpack:

1. Common JS support
2. NPM support
3. a healthy loader/plugin ecosystem.

Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.