Skip to content

Release Notes: Sprint 20

Jump to bottom
peterflynn edited this page Feb 3, 2013 · 11 revisions

This is a draft! Release notes for Sprint 20 will be finalized at the end of the sprint, around 2/12/13.

What's New in Sprint 20

  • Code Editing
    • Migrated to CodeMirror 3: This enables many of the benefits listed below
    • Undo restores old selection / cursor position much more reliably
    • Granularity of Undo steps is more predictable
    • Gutter line numbers stay in view when scrolling horizontally
    • Newlines are no longer added when certain closing tags are auto-inserted (we may bring this back as a preference in a future build)
    • Double-click-drag and triple-click-drag to select multiple words/lines quickly
    • CSS code coloring is more colorful
    • Haxe syntax highlighting
  • Search
    • All Find results are highlighted while search bar is open
    • Current result is centered in the viewport instead of often appearing at its edges (Find, Find in Files, Quick Open, etc.)
    • Quick Open / Go to Definition results update even faster as you type incrementally (building on last sprint's improvements)
  • Code Hinting
    • CSS code hinting is less aggressive - it will pop up once you start typing a property name, but not before then (unless you explicitly press Ctrl+Space)
    • Bug fix: CSS code hinting now works in inline editors

Full change logs: brackets and brackets-shell

UI Changes

API Changes

Editor offsetTopChanged event removed - This was deprecated in sprint 19 and has been removed in sprint 20.

New/Improved Extensibility APIs

Quick Open providers - The provider's search() method is now passed an additional argument, stringMatcher. Using stringMatcher.match() instead of QuickOpen.match() will yield improved performance through caching. You can also cache your own data by adding properties to this object; see extensions/default/QuickOpenHTML/main.js for sample usage. Use of this argument is optional.

Known Issues

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

Community contributions to Brackets

Contributions from Brackets

Bugs fixed in Sprint 20

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

Clone this wiki locally