Cleanups, mainly to unit tests:
- Improve docs in SpecRunnerUtils
- Add assertion in SRU in case a mock Document is created without an Editor
but then used in a way that would auto-create an Editor (which won't get
cleaned up)
- Add assertion in _destroyEditorIfUnneeded() since its name makes it easy
to call with the wrong type (including via SRU.destroyMockEditor())
- Rename HTML code hints suite & remove unused var
- Minor docs cleanups in LanguageManager (incorrect usage of "i.e.", missing
docs for new fileNames option, etc.)
- Add unit tests for install dialog cases where installer comes back with a
result after clicking Cancel but before Cancel times out, or comes back
vary late after timeout once user has opted to close the dialog
- Remove a duplicated LanguageManager test (due to f67cfcdf)
- Add a few more StringMatch tests to ensure tricky cases don't break in
the opposite direction as before
Cleanups:
* DocumentManager: use CollectionUtils.forEach() in notifyPathNameChanged()
(removing early-exit optimization that's probably unneeded; can reintroduce
when CollectionUtils.some() lands)
* Move filename->language mapping tests from Editor-test to LanguageManager-test
* Add another #330 testcase as suggested by Glenn in #3064
* Add StringMatch testcases as suggested by Kevin in #3417
* SpecRunnerUtils: use waitsForDone() more
* CSSUtils-test: remove unused vars
* Dialogs: tiny docs improvement
bump to 15,000 for now
Fixed directory already exists issue
Merge branch 'duplicate-directory-dialog-fix' into directory-creation-error
add a check to see if we need to scroll the result or not for the first match
remove 'return' statement to allow Brackets to fall thru to rest of New File code b/c we've already force completed the previous rename
more better way -- works perfectly so far :)
update comment
Merge branch 'master' into jeff/fix-find-result-centering-rebased
Implemented code review suggestions
Finished code review fixes
Added variables to strings
move inline js into external files
add std license header and placate jslint
reorganize Readme

Moved paragraphs around so least technical (most user-oriented) is on top, then tech/contributing (hacker info) is near the end.  This allowed to streamline the prose, but I tried to avoid changing the text as much as possible.

Linked blog in welcome section (great for finding features; helps users decide if Brackets is for them).

Used H4 vs **bold** for sub-headers.
more terse, less repeated text

(note to self; don't Push with only 4 hours of sleep)
more terse, less repeated text, ordered helping steps
add comment for future about no inline scripts
Fix #4333 (files shown as plain text incorretly).

- Added FileUtils.getBaseName (jsdoc and unit tests included).
- Replace usage of path-utils.js with getBaseName.