Release Notes: Sprint 39

This is a draft!

This document will not be finalized until the end of Sprint 39 -- approximately May 5.

What's New in Sprint 39

• File Types
  • Customize file extension -> language/syntax mode mapping: Set language.fileExtensions or language.fileNames to a map object whose keys are file extensions/names and whose values are language IDs. See how to edit your preferences file.
  • Switch language/syntax mode of a single file: Use the language indicator in the status bar as a dropdown to override the language Brackets chose to treat a file as. (These changes are not saved when you close the file; use the preferences above to permanently treat all files with a certain extension as a different language).
  • Windows: Filter out binary files and unsupported encodings: Speeds up Find in Files for certain projects, and reduces clutter in the Quick Open file list. Attempting to open a non-UTF-8 file now results in an error instead of showing garbled text. (This was already implemented on other platforms).
• Code Editing
  • Cut/Copy whole line when nothing is selected
• CSS Editing
  • Fuzzy/camelCase code hints: Code hints now use smart string matching, similar to Quick Open and JS code hints -- for example, you can type "btr" to see an autocompletion hint for border-top-right-radius.
• Extensions
  • Extension update notifications: The Extension Manager toolbar icon turns green when one or more of your installed extensions have a new version available.
  • Admin features for Extension Registry: (available since 4/17) An extension's author can delete the extension from the registry, mark the extension as incompatible with newer versions of Brackets, or transfer ownership to a different author.
• OS Support
  • Windows XP is no longer officially supported by Brackets. It is still possible to download and install Brackets on Windows XP, but we will no longer test it - so future versions may become completely incompatible without warning.
• Ongoing Research (not implemented yet)
  • Research: Split-view architecture: See architecture proposal.
  • Research: Theming support

Full change logs: brackets and brackets-shell

UI Changes

Find menu added - All Find/Replace-related menu items have been moved from the Edit menu to a new Find top-level menu.

Non UTF-8 encodings - On Windows, earlier Brackets versions would open files with other encodings even though the file could not be displayed or saved correctly. Brackets now shows an error message and refuses to open the file, matching Mac versions of Brackets.

API Changes

Find commands - Find/Replace-related command ID constants (Commands.EDIT_FIND* and a few others) have been deprecated: use Commands.CMD_FIND* (and similar) instead. The raw ID string values have changed, so if you're using them instead of referencing the constants, your code will be broken immediately.

The menu item group constants Menus.MenuSection.EDIT_FIND_COMMANDS/EDIT_REPLACE_COMMANDS are deprecated: use Menus.MenuSection.FIND_FIND_COMMANDS/FIND_REPLACE_COMMANDS instead. Using the old constants will add your menu items to the end of the Edit menu.

New/Improved Extensibility APIs

Find menu - Use Menus.AppMenuBar.FIND_MENU to add menu items to the new Find top-level menu.

Known Issues

• Activity Monitor in Mavericks (OS X 10.9) says the Brackets Helper process is "Not Responding" even when it's working normally (#5794). You can safely ignore this unless Brackets is actually failing to respond when you click or type text.
• #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.
• #4362: Slow startup of Brackets and Live Preview on Windows due to Chrome proxy settings. See workaround.
• 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.
• #7127: With Chrome 34, using Live Preview will show a console error: "'CSS.getAllStyleSheets' wasn't found". This is harmless and shouldn't affect Live Preview.

Community contributions to Brackets

TODO

Pulling source code from Git

TODO...

• Some submodules were updated this sprint. Run git submodule update to ensure your source tree is fully up to date.

Bugs fixed in Sprint 39

For details on the bugs addressed, please refer to closed sprint 39 bugs. Not all fixed bugs will be caught by this search query, however.