Skip to content

Instantly share code, notes, and snippets.

// These might be good globals
line1: {
overflow: 'hidden',
display: '-webkit-box',
textOverflow: 'ellipsis',
WebkitLineClamp: 1,
WebkitBoxOrient: 'vertical'
},
line2: {
overflow: 'hidden',
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>environment</string>
<key>ProgramArguments</key>
<array>
<string>sh</string>
<string>-c</string>
@gabriel
gabriel / installer.rb
Last active January 2, 2016 16:09
Install a test target
require 'xcodeproj'
require 'xcodeproj/ext'
require 'fileutils'
project_path = "TheProj.xcodeproj"
project_name = "TheProj"
test_project_name = "#{project_name}Tests"
FileUtils.mkdir_p(test_project_name)
File.open("#{test_project_name}/main.m", "w") do |f|
Pod::Spec.new do |s|
s.name = "CryptoPill"
s.version = "1.0.1"
s.summary = "CryptoPill is the crypto code used by Core Secret"
s.homepage = "https://github.com/seb-m/CryptoPill"
s.license = 'MIT'
s.author = { "Sébastien Martini" => "seb@dbzteam.org" }
s.source = { :git => "https://github.com/seb-m/CryptoPill", :tag => "1.0.1" }
s.platform = :ios, '7.0'
@gabriel
gabriel / gist:6998753
Last active December 25, 2015 15:29
Coworking spaces with dedicated desk, 24/7 access
Galvanize (1st & Howard)
http://www.galvanize.it/
$599
WeWork (2nd & Mission, 6th & Market)
https://www.wework.com/sf/soma
$400 ($600-$700 private)
Parisoma (11th & Howard)
http://www.parisoma.com/coworking/
@gabriel
gabriel / prever.md
Last active December 16, 2015 21:42

Prereleases

Versioning

We use a semantic versioning string, that looks like 1.2.3 or 1.2.3-400 or 1.2.3-400+comment. After the dash (-) is the "prerelease" info. After the plus (+) is a comment field.

There are two ways to set the build number:

Verifying that +gabrielh is my blockchain ID. https://onename.com/gabrielh

Proposal for release versioning

  • We use a semantic versioning (e.g. 1.2.3-400)
  • Major, minor or patch only get incremented on production releases, 1.2.3 -> 1.2.4 or 1.3.1 or 2.0.0.The build number can be omitted or hidden when displaying this release version to humans. Code always passes around full version string.
  • We have a build version, that gets incremented on any packaged build, for testing (1.2.3-400) -> (1.2.3-401).
  • Obviously follow conventions for when to increment major, minor or patch
  • Staging releases are test releases so they increment build number

Upsides

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js"></script>
<script>
var accumulatedX = null;
var accumulatedY = null;
var smoothing = 0.95;
def _fetch(self, url, retry_count, **kwargs):
"""Calls urlfetch.fetch with retry count"""
try_count = 0
times = []
response = None
while try_count < retry_count:
try:
try_count += 1
# Fetch the url