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

• Code Editing
  • 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 yet saved when you close the file, or generalized to all files with a certain extension).
  • Cut/Copy whole line when nothing is selected
• Search
  • File exclusion filters for Quick Open, Quick Edit, and JS Code Hints: Similar to the filtering already available for Find in Files. TODO: details
• Extensions
  • 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.
• Ongoing Research (not implemented yet)
  • Research: Split-view architecture: See architecture proposal.

Full change logs: brackets and brackets-shell

UI Changes

TODO - Edit/Search menu change

API Changes

TODO

New/Improved Extensibility APIs

TODO

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.
• On Windows XP, Brackets will not detect external file changes instantly. It behaves similarly to Sprint 35 and earlier releases - changes are detected upon window activation, and the folder tree must be manually refreshed.
• #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.