Release Notes: 1.0

This is a draft!

This document will not be finalized until the end of Release 1.0 -- approximately November 3.

What's New in Release 1.0

• Preferences
  • Configure keyboard shortcuts: Users can now customize keyboard shortcuts for internal Brackets commands. See https://github.com/adobe/brackets/wiki/User-Key-Bindings for more information.
• Stylesheet Editing
  • Collapse unwanted Quick Edit results: Quickly collapse results from a particular CSS, SCSS, or LESS file. For example, when using a preprocessor you can hide results from the compiled CSS file to focus on results in your original SCSS/LESS code.
• Hint List Searching
  • javascript hinting is more accurate: Hint-List searching now gives greater weight to Matching by Case so "function" is weighted higher than "Function".
  • Auto-install bundled extensions: Add mechanism to automatically install extensions in auto-install-extensions to allow installation "bundles".

Full change logs: brackets and brackets-shell

UI Changes

• Brackets running on Yosemite (OSX 10.10) now has a Yosemite look with flat traffic light buttons. The full-screen button moves to the green traffic light button on Yosemite as well.

• Brackets now works with auto-hide Task Bars on Windows with Maximized windows.

API Changes

There were no API changes in this release. A wiki on best practices for programmatically opening files in Brackets was published: https://github.com/adobe/brackets/wiki/Programmatically-Opening-Files-in-Brackets

New/Improved Extensibility APIs

Themes - Themes no longer need to include a dummy 'main.js' file. Theme authors may wish to continue including this file in the short term for compatibility with Brackets 0.44, however.

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.
• 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.

Community contributions to Brackets

TODO

Pulling source code from Git

• Recommended: rebuild or reinstall an updated brackets-shell (new functionality was added).
• Some submodules were updated this sprint. Run git submodule update to ensure your source tree is fully up to date.

Bugs fixed in Release 1.0

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