Last tested using Mac OS X 10.8 Mountain Lion
Copy Dropbox folder from previous drive to user folder
<!-- http://www.brucelawson.co.uk/2010/a-minimal-html5-document/ --> | |
<!doctype html> | |
<html lang=en> | |
<head> | |
<meta charset=utf-8> | |
<title>blah</title> | |
</head> | |
<body> | |
<p>I'm the content</p> |
<meta name="viewport" content="width=320"> | |
<meta name="viewport" content="width=device-width"> | |
<meta name="viewport" content="initial-scale=1"> | |
<meta name="viewport" content="maximum-scale=1"> | |
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1"> |
{ | |
"folders": | |
[ | |
{ | |
"path": "root-project-folder", | |
"folder_exclude_patterns": ["css", ".sass-cache"] | |
} | |
] | |
} |
function MyObject(options) { | |
/***************************************** | |
/* PRIVATE VARS | |
/****************************************/ | |
var self = { | |
} |
# Meteor working with accounts | |
# Getting the current user id | |
user = Meteor.userId() | |
# Run some stuff whenever a cursor or session changes | |
Meteor.startup -> | |
Meteor.autorun -> | |
if not Session.get('selected') | |
party = Parties.findOne() |
// Replaces all of Vote.users array | |
Votes.update( | |
{_id: '32dc6fa5-052e-4e2c-8a90-4bd235bf3b0d'}, | |
{ | |
$set: { | |
'users': [ | |
{ | |
id: '2f537a74-3ce0-47b3-80fc-97a4189b2c15', | |
vote: 0 | |
}, |
Below is an excerpt from http://nicolasgallagher.com/about-html-semantics-front-end-architecture/ explaining why you would want to use multiple related classes on an element vs. one class that gets extended in the CSS.
Components often have variants with slightly different presentations from the base component, e.g., a different coloured background or border. There are two mains patterns used to create these component variants. I’m going to call them the “single-class” and “multi-class” patterns.
.btn, .btn-primary { /* button template styles */ }
# Reference jQuery | |
$ = jQuery | |
# Adds plugin object to jQuery | |
$.fn.extend | |
# Change pluginName to your plugin's name. | |
pluginName: (options) -> | |
# Default settings | |
settings = | |
option1: true |