happycollision

#!/bin/sh                        

####################################
#  Output file for HTML5 video    #
#  Requirements:                  #
#    - handbrakecli               #
#    - ffmpeg                     #
#    - ffmpeg2theora              #
#                                 #
#  usage:                         #

happycollision

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

# This Vagrantfile (vagrantup.com) spins up a MySQL server with your data 
# already loaded. Many of the settings below are the same suggestions you get
# from `vagrant init`.
#
# Just be sure that (if you want data loaded) you have your .sql file sitting
# in the directory that will be shared to the guest. Usually this is the folder
# that your Vagrantfile is in. The database and user will have the same name as

happycollision

/*

Find Window Ratio
By Don Denton
don@happycollision.com

For example, a 16:9 ratio:

1. Copy/paste this whole thing into your console and hit enter/return.
2. Then use the command `findWindowRatio(16,9)` to find a viewport size

happycollision

// This gist is based on @wnstn's great [gist](https://gist.github.com/wnstn/36010c8378e850cc3580) 
// and @maykefreitas's [advice](https://github.com/BrowserSync/browser-sync/issues/977#issuecomment-236443965) about turbolinks.

// Code below is generated after running `browser-sync init` in your project's root directory.
// I commented the lines I changed or added so you can run it from scratch as well, if you like.


/*
 |--------------------------------------------------------------------------
 | Browser-sync config file

happycollision

import Ember from 'ember';

export default Ember.Controller.extend({
});

happycollision

const Settings = {
    firstNameFocus: m("Settings", "First Name", "Component Interaction", "Begin"),
    firstNameChange: m("Settings", "First Name", "Component Interaction", "Update"), // ??? maybe add this directly to the call?

    changePasswordClick: m("Settings", "Password Change", "Component Interaction", "View"),
    passwordCurrentFocus: e("Password Change", "Current Password", "Component Interaction", f(value, beginOrUpdate)),
    passwordNewFocus: e("Password Change", "New Password", "Component Interaction", f(value, beginOrUpdate)),
    passwordNewConfirmFocus: e( "Password Change", "New Password Confirm", "Component Interaction", f(value, beginOrUpdate) ),
    passwordSubmitBtnClick: m("Password Change", "Update Password", "Component Interaction", "Update"),
    passwordCancelBtnClick: m("Password Change", "Cancel", "Component Interaction", "Hide"), // Btn does not exist. It should.

happycollision

// The purpose of this script is to check if `npm run <user-script>` will exit
// with the proper exit code if the script fails. We cannot trust anything if
// exit codes are not respected. I mean... just imagine...
//
//     npm run test && npm run deploy
//
// See the following to understand this level of paranoia:
//
// https://github.com/npm/npm/issues/14339
// https://github.com/npm/cli/issues/6399