| import React from 'react' | |
| import SearchableSelect from 'part:@sanity/components/selects/searchable' | |
| import FormField from 'part:@sanity/components/formfields/default' | |
| import {PatchEvent, set, unset} from 'part:@sanity/form-builder/patch-event' | |
| const STREET_NAMES = [ | |
| 'Thorvald Meyers gate', | |
| 'Champs-Élysées', | |
| 'Lombard Street', | |
| 'Abbey Road', |
I'm going to write down my thoughts on these two libraries that I'm conflicted between.
Disclaimer: These are just my personal stream of consciousness notes and not meant to be a well thought through blog post/opinion piece. Both these libraries are fantastic and the authors deserve huge props/respect. If you find these musings helpful I'm glad, but I encourage you to take it with a grain of salt.
Permalink: git.io/vps
| Provider | Type | RAM | Cores | Storage | Transfer | Network | Price |
|---|
| /** | |
| * A very lightweight version of Meteor's Minimongo collections, | |
| * a local store for records sent from the Meteor backend. | |
| */ | |
| var LocalCollection = function() { | |
| this._initialize(); | |
| }; | |
| _.extend(LocalCollection.prototype, Backbone.Events, { | |
| _name: null, |
| (function() { | |
| Backbone.Events.autorun = function(f, context) { | |
| if (!this.__autorunHandles) this.__autorunHandles = []; | |
| var backboneContext = this; | |
| var handle = Tracker.autorun(function() { | |
| Tracker.currentComputation.__backboneContext = backboneContext; | |
| f(); | |
| }); | |
| this.__autorunHandles.push(handle); | |
| return handle; |
| Form.editors.SortableList = Form.editors.List.extend({ | |
| initialize: function() { | |
| Form.editors.List.prototype.initialize.apply(this, arguments); | |
| }, | |
| render: function() { | |
| Form.editors.List.prototype.render.apply(this, arguments); | |
| // sorting | |
| if (!this.sortable) { |
If you're like me you have a dir like ~/Workspace/Github where all your git repos live. I often find myself making a change in a repo, getting side tracked and ending up in another repo, or off doing something else all together. After a while I end up with several repos with modifications. This script helps me pick up where I left off by checking the status of all my repos, instead of having to check each one individually.
Usage:
git-status [directory]This will run git status on each repo under the directory specified. If called with no directory provided it will default to the current directory.
| // Marionette.Gauntlet v0.0.0 | |
| // -------------------------- | |
| // | |
| // Build wizard-style workflows with an event-emitting state machine | |
| // Requires Backbone.Picky (http://github.com/derickbailey/backbone.picky) | |
| // | |
| // Copyright (C) 2012 Muted Solutions, LLC. | |
| // Distributed under MIT license | |
| // Modifications by Tim Shnaider | |
| // |
| node_modules: Makefile | |
| @rm -rf $@ | |
| @mkdir -p $@ | |
| $(call get_src_module,$@,https://github.com/tastapod/node-imap/tarball/bruno-merge) | |
| $(call get_npm_module,$@,log,1.2.0) | |
| $(call get_npm_module,$@,connect,1.8.2) | |
| # We have to manually fetch connect's dependencies | |
| $(call get_npm_module,$@,qs,0.4.0) | |
| $(call get_npm_module,$@,mime,1.2.4) | |
| $(call get_npm_module,$@,formidable,1.0.8) |
