| extension UIView { | |
| func addConstaintsToPinHorizontalEdgesToSuperView(padding: CGFloat = 0) { | |
| prepareForConstraints() | |
| self.superview!.addConstraints(NSLayoutConstraint.constraintsWithVisualFormat("H:|-(padding)-[view]-(padding)-|", | |
| options: NSLayoutFormatOptions(0), | |
| metrics: ["padding":padding], | |
| views: ["view":self])) | |
| } | |
| func addConstaintsToPinVerticalEdgesToSuperView(padding: CGFloat = 0) { |
| #!/usr/sbin/dtrace -q -s | |
| /* | |
| Overly spammy, mostly covered by the other probes (every "read" or "write" is a "request") | |
| CFPreferencesServer$target:::request { | |
| printf("REQUEST from pid %d at %Y ( domain: %s, user: %s, host: %s, container: %s, managed: %d)\n", arg0, walltimestamp, copyinstr(arg1) != NULL ? copyinstr(arg1) : "(NULL)" ?: "(NULL)", copyinstr(arg2) != NULL ? copyinstr(arg2) : "(NULL)", copyinstr(arg3) != NULL ? copyinstr(arg3) : "(NULL)", copyinstr(arg4) != NULL ? copyinstr(arg4) : "(NULL)", arg5); | |
| } | |
| */ | |
| CFPreferencesServer$target:::write_rejected { | |
| printf("REJECTED WRITE OF KEY %s request from pid %d for reason %s at %Y ( domain: %s, user: %s, host: %s, container: %s)\n", copyinstr(arg1) != NULL ? copyinstr(arg1) : "(NULL)", arg0, copyinstr(arg6) != NULL ? copyinstr(arg6) : "(NULL)", walltimestamp, copyinstr(arg2) != NULL ? copyinstr(arg2) : "(NULL)", copyinstr(arg3) != NULL ? copyinstr(arg3) : "(NULL)", copyinstr(arg4) != NULL ? copyinstr(arg4) : "(NULL)", copyinstr(arg5) != NULL ? copyinstr(arg5) |
| #!/usr/bin/env bash | |
| # | |
| # Originally from https://gist.github.com/IanVaughan/2902499 | |
| # | |
| # authors: Ian Vaughan | |
| # Jacob Zimmerman | |
| # | |
| # usage: uninstall_gems [<version> ...] | |
| # | |
| # examples: |
#Container Resource Allocation Options in docker-run
now see: https://docs.docker.com/engine/reference/run/#runtime-constraints-on-resources
You have various options for controlling resources (cpu, memory, disk) in docker. These are principally via the docker-run command options.
##Dynamic CPU Allocation
-c, --cpu-shares=0
CPU shares (relative weight, specify some numeric value which is used to allocate relative cpu share)
| extension YapDatabaseView { | |
| public enum Grouping { | |
| case ByKey(YapDatabaseViewGroupingWithKeyBlock) | |
| case ByObject(YapDatabaseViewGroupingWithObjectBlock) | |
| case ByMetadata(YapDatabaseViewGroupingWithMetadataBlock) | |
| case ByRow(YapDatabaseViewGroupingWithRowBlock) | |
| var object: YapDatabaseViewGrouping { |
The final result: require() any module on npm in your browser console with browserify
This article is written to explain how the above gif works in the chrome (and other) browser consoles. A quick disclaimer: this whole thing is a huge hack, it shouldn't be used for anything seriously, and there are probably much better ways of accomplishing the same.
Update: There are much better ways of accomplishing the same, and the script has been updated to use a much simpler method pulling directly from browserify-cdn. See this thread for details: mathisonian/requirify#5
| git config --global diff.tool bbdiff | |
| git config --global difftool.bbdiff.cmd 'bbdiff --wait --resume "$LOCAL" "$REMOTE"' | |
| git config --global difftool.prompt false | |
| git config --global merge.tool bbdiff | |
| git config --global mergetool.bbdiff.cmd 'bbdiff --wait --resume "$LOCAL" "$REMOTE"' | |
| Double check ~/.gitconfig |
| // Open Script Editor and Export this as an Application | |
| // | |
| // Then drop a keynote file on it in the Finder and it will properly resize | |
| // and rotate everything so the Keynote file becomes usable as a prototype | |
| // in the iPhone keynote app | |
| // rotateDocument exported function | |
| // | |
| // Accepts a Keynote document and will rotate | |
| // all the slides and elements in the slide 90 degrees |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
