sudo atsutil databases -remove
atsutil server -shutdown
atsutil server -ping
from http://doc.extensis.com/Font-Management-in-OSX-Best-Practices-Guide.pdf
@font-face { | |
font-family: "SF Pro Text"; | |
font-style: normal; | |
font-weight: 300; | |
src: url("https://raw.githubusercontent.com/blaisck/sfwin/master/SFPro/TrueType/SFProText-Light.ttf"); | |
} | |
@font-face { | |
font-family: "SF Pro Text"; | |
font-style: normal; | |
font-weight: 400; |
sudo atsutil databases -remove
atsutil server -shutdown
atsutil server -ping
from http://doc.extensis.com/Font-Management-in-OSX-Best-Practices-Guide.pdf
This is probably going to be the next iteration of the declarative CRUD metamodel that powers Hyperfiddle. It's just a design sketch, the current metamodel in prod is different. Hyperfiddle is an easy way to make a CRUD app. Hyperfiddle is based on Datomic, a simple graph database with the goal of "enabling declarative data programming in applications."
This extends Datomic pull syntax into something that composes in richer ways. The key idea is that Pull notation expresses implicit joins and thus can be used to declare data dependencies implicitly, without needing to name them. We also handle tempids, named transactions, and hyperlinks to other pages. We satisfy the hypermedia constraint, like HTML and the web.
{identity ; Pass through URL params to query
[{:dustingetz/event-registration ; virtual attribute identif
First we'll update your local master branch. Go to your local project and check out the branch you want to merge into (your local master branch)
$ git checkout master
Fetch the remote, bringing the branches and their commits from the remote repository. You can use the -p, --prune option to delete any remote-tracking references that no longer exist in the remote. Commits to master will be stored in a local branch, remotes/origin/master
/* -------------------------------- | |
Typography | |
-------------------------------- */ | |
:root { | |
--font-primary: sans-serif; | |
--font-secondary: serif; |
/* Shadow 0dp */ | |
box-shadow: none; | |
/* Shadow 1dp */ | |
box-shadow: 0 1px 1px 0 rgba(0,0,0,0.14), 0 2px 1px -1px rgba(0,0,0,0.12), 0 1px 3px 0 rgba(0,0,0,0.20); | |
/* Shadow 2dp */ | |
box-shadow: 0 2px 2px 0 rgba(0,0,0,0.14), 0 3px 1px -2px rgba(0,0,0,0.12), 0 1px 5px 0 rgba(0,0,0,0.20); | |
/* Shadow 3dp */ |
A combination of my own methodology and the Web Application Hacker's Handbook Task checklist, as a Github-Flavored Markdown file
Objective | Step | Description |
---|---|---|
Process the Problem | Understand the Problem |
|
Examples/Test Case | Validate understanding of the problem | |
Data Structure | How we represent data that we will work with when converting the input to output. | |
Algorithm | Steps for converting input to output | |
Code with Intent | Code | Implementation of Algorithm |
def sum_of_multiples(target, factors) | |
multiples = [] | |
factors = [3, 5] if factors.length == 0 | |
factors.each do |factor| | |
current_multiple = factor | |
while current_multiple < target | |
multiples << current_multiple | |
current_multiple += factor |