Release Notes: Sprint 21

This is a draft!

This document will not be finalized until the end of Sprint 21 -- approximately March 1.

Code Hinting
- JavaScript code hinting: Smart code hinting includes keywords, local variables, arguments, and property names based on nearby code.
Live Development
- Default localhost for Live Preview: By default, Live Preview now launches an http://localhost URL instead of file:// thanks to a build-in Node.js server. Pointing Live Preview at your own local server remains supported (see File > Project Settings).
Overall UI
- Drag & drop to open files: Drag files onto the Dock icon (on Mac) or the Brackets window itself (on Windows) to open them.
- Remember cursor & scroll position across launches: Files you leave open when you quit or switch projects will be reopened right where you left off. Within a session, this also works for files you open, close, then reopen later.
Extensions
- Enables language extensions: New file types can be added by extensions, with support for syntax highlighting, block/line comments, and more.

Full change logs: brackets and brackets-shell

No major changes to existing features.

Editor constructor - The mode argument has been removed, shifting other arguments over (mode is now retrieved from the Document). Note: it would be very unusual for an extension to be calling the Editor constructor directly.
Debug menu - Removed Menus.AppMenuBar.DEBUG_MENU menu ID
EditorUtils removed - EditorUtils.getModeFromFileExtension() changed to Languages.getLanguageForFileExtension()
LanguageManager and Language - LanguageManager allows extensions to define new language support in Brackets without making modifications to core Brackets code. In this first iteration, a Language can be defined declaratively in JSON as a set of properties including a CodeMirror syntax highlighting mode, file extensions to map to the language, and finally line and block commenting syntax. Optionally, extensions may define custom CodeMirror modes. For an overview of language support and our future direction please see the wiki.

#1551: Changes within an extension (or a unit test) are not reflected by a simple "Debug > Reload Brackets." Workarounds:
- Quit and re-launch Brackets to pick up the changes.
- Open Developer Tools, click the gear icon in the lower-right, and select "Disable cache." This setting is remembered, but is only in effect so long as the Developer Tools browser tab remains open.
Debug > Run Tests is disabled in the installer/DMG distributions of Brackets, because the unit test code is not included. To run unit tests, pull Brackets from GitHub instead.
Mountain Lion (OS X 10.8) by default will not allow Brackets to run since it's not digitally signed yet. To work around this, right click the Brackets app and choose Open. You only need to do that once -- afterward, launching Brackets the normal way will work also.
#2272: Windows Vista may not allow the Brackets installer to run (you may not see any error message). To work around this, right-click the installer file, choose Properties, and click the Unblock button.

For details on the bugs addressed, please refer to closed sprint 21 bugs. A few of the fixed bugs might not be caught by this search query, however.