| gitflow | git |
|---|---|
git flow init |
git init |
git commit --allow-empty -m "Initial commit" |
|
git checkout -b develop master |
| git config --global merge.tool p4merge | |
| git config --global mergetool.p4merge.path "C:/Program Files/Perforce/p4merge.exe" |
| /** | |
| * This code is licensed under the terms of the MIT license | |
| * | |
| * Deep diff between two object, using lodash | |
| * @param {Object} object Object compared | |
| * @param {Object} base Object to compare with | |
| * @return {Object} Return a new object who represent the diff | |
| */ | |
| function difference(object, base) { | |
| function changes(object, base) { |
This section describes the conventions used here to describe type signatures.
A [T] is an array-like value (only ever used read-only in this API), i.e., one with an integer length and whose indexed properties from 0 to length - 1 are of type T.
A type T? should be read as T | undefined -- that is, an optional value that may be undefined.
This section describes the conventions used here to describe type signatures.
A [T] is an array-like value (only ever used read-only in this API), i.e., one with an integer length and whose indexed properties from 0 to length - 1 are of type T.
A type T? should be read as T | undefined -- that is, an optional value that may be undefined.
The question: how can we use ES6 modules in Node.js, where modules-as-functions is very common? That is, given a future in which V8 supports ES6 modules:
- How can authors of function-modules convert to ES6
exportsyntax, without breaking consumers that dorequire("function-module")()? - How can consumers of function-modules use ES6
importsyntax, while not demanding that the module author rewrites his code to ES6export?
@wycats showed me a solution. It involves hooking into the loader API to do some rewriting, and using a distinguished name for the single export.
This is me eating crow for lots of false statements I've made all over Twitter today. Here it goes.
| using UnityEngine; | |
| using UnityEditor; | |
| using System; | |
| using System.Reflection; | |
| public class WebWindow : EditorWindow { | |
| static Rect windowRect = new Rect(100,100,800,600); | |
| static BindingFlags fullBinding = BindingFlags.Public | BindingFlags.NonPublic | BindingFlags.Instance | BindingFlags.Static; | |
| static StringComparison ignoreCase = StringComparison.CurrentCultureIgnoreCase; |
| /* License MIT */ | |
| var spawn = require( 'child_process' ).spawn, | |
| colors = require( 'colors' ); | |
| /* | |
| Executes a command and fires event when done that | |
| will return the command output | |
| */ | |
| function system( cmd ){ |
As I worked with Y.App it became clear that while Y.View is a great abstraction it would be easy to overwhelm a single instance with way too much functionality. This is my attempt to solve that issue by allowing multiple child views to be attached to a single parent view via an extension.
The extension is mixed into the parent view like any other extension using Y.Base.create.
var Parent = Y.Base.create("view", Y.View, [