* Many packager improvements; Windows signing!
* Windows signing works now! (Certs are on an external USB stick that
must be plugged into the build machine during build. We can't do the
same for OS X because certs need to exist in the login Keychain to be
found.)
Fixes#219
* Signing is now optional (so OS X and Windows contributors can run
`npm run package` without errors)
* zip, dmg, and deb arguments are now passed in as e.g. "--package=dmg"
* Print a huge warning when signing is disabled so we're less likely to
ship unsigned binaries to users.
* Make console.logs during packaging consistent and parallel
("creating..." followed by "created.")
* More aggressive signing warnings
* Warn when building OS X app on non-OS X platform (because signing
will never work on non-OS X platforms)
* Warn when building Windows app on non-Windows platform (because
signing doesn't work yet on non-Windows platforms)
* issue template
* cleanup closePlayer() and stopServer()
* Add subtitle support (via drag-n-drop)
Drag and drop a subtitles file (.srt or .vtt) onto the player (or the
app icon on OS X) to add subtitles to the currently playing video.
For #281
* add multiple subtitles structure
* add open subtitle dialog from cc player controls
* Separate hidden window, with its own renderer process, for WebTorrent
(Must be a window. You cannot run WebRTC at all in a Web Worker, and you can't
run it well in a node process like the electron main process.)
* Disabled the create-torrent-modal for now. That gives us a consistent UX
regardless of whether the user dragged files or folders onto the app or opened
the Create New Torrent menu item.
* Main process routes all messages between the main and webtorrent windows.
* The renderer index.js is smaller now (but still too big), with the WebTorrent
interface moved to webtorrent.js / it's own process.
* The UI should be faster now, and should not lag under load.
webtorrent-www relies on this name. I originally changed it because I
thought the windows install builder was using it, but I pass all the
options into that explicitly now, and even pass an option to prevent it
from using package.json, so this should be okay.
