* Step 1: move electorn into `app/`.
This is to comply with the suggested directory format of
`electron-builder`: https://github.com/electron-userland/electron-builder#two-packagejson-structure
* Step 2: add build directory with icon files for mac / windows
* Step 3: move all development (web) assets into main directory
* Step 4: add `build` namespace to dev `package.json`
* Step 5: move all dev dependencies into dev file and get rid of
old electron packagers in favor of `eletorn-builder`
* Step 6: target build inside `app/` as everything else is excluded at build time
* Step 7: remove old stuff!
* Step 8: update README
* turn off asar for `child_pty`
* Allow the `color` config to be an object
It only covers the ANSI 16 as named colors, but allows for an array to
be used if the full color palette wants to be overridden.
* Better handling for array color configs vs. object configs
* Add support for a `registry` configuration field
For those of us using a system-wide private registry, this helps by allowing hyperterm to bypass it when installing/updates plugins.
* Use getDecoratedConfig()
* registry -> npmRegistry
* no message
* Add an option for a non-login shell to be run
By default, however, the user's login shell will be used
* Reset shell default to empty string, and improve documentation
