adobe/brackets — pull request #6622 by jasonsanjose (2014-01-23 20:22:03+00:00)
Title: [REVIEW ONLY] Prototype launching browser via node domain

TODO clean up Firefox instructions

To get FirefoxAurora working:

1. Follow instructions from https://github.com/auchenberg/remotedebug-firefox-bridge#getting-started and https://github.com/auchenberg/remotedebug-firefox-bridge/issues/3
2. Once remote debugging is on, open `file:///Applications/Brackets.app/Contents/dev/src/LiveDevelopment/launch.html`
3. In Brackets, open live preview

To use

Launching
- [x] Replace our `brackets.app.openLiveBrowser` and `brackets.app.closeLiveBrowser` with a node domain that uses `child_process` to execute programs from node

Preferences
- [ ] Remove hardcoded Mac paths
- [x] Setup basic prefs for Chrome/Canary/FirefoxAurora
- [ ] Save prefs to `user` scope for easier access @dangoor
- [ ] Do not clobber `user` scope prefs if they already exist

UI
- [ ] Display browsers in a menu?
- [ ] Set default browser, see `isDefault` flag

Populate default browsers at first launch
- [ ] Windows - use `REG` to find path to `chrome.exe`
- [ ] Mac - use `mdfind "kMDItemCFBundleIdentifier == 'com.google.Chrome'"` to find Chrome
- [ ] Mac - use `codesign --display /Applications/Google\ Chrome.app` to get to binary in app bundle
- [ ] Linux - Find path to exe or just rely on `$PATH`?

Code cleanup
- [ ] Make `ChildProcess` API match node `child_process`
- [ ] Error handling