Skip to content

Release Notes: Sprint 36

Peter Flynn edited this page Mar 5, 2014 · 22 revisions

What's New in Sprint 36

Full change logs: brackets and brackets-shell

UI Changes

Scrollbars - Scrollbars on all versions of Windows now have a flatter, Windows-8-style appearance that matches the overall Brackets UI design better.

CSS code hints - When selecting a property name hint, a space is now automatically inserted after the ":".

API Changes

FileSystem - Nothing needs to change for most code; the public FileSystem APIs are unchanged except for the "change" event (see docs for details). All file operations automatically receive the benefits of caching, and all Document objects are automatically updated (firing appropriate events) when file watchers detect an update.

The API for developing an alternative file system implementation has changed, however.

Linting - The process for registering a linter is unchanged, but it's now possible to register more than one linter per file type. (Except that, as before, the built-in JSLint provider is automatically disabled when any other JS linter is registered).

The result yielded by CodeInspection.inspectFile() has changed: instead of a single linter result, it now returns an array of objects, each containing the result of one specific linter.

CSS tokens - The latest version of CodeMirror parses CSS files differently. If you rely on the raw tokens emitted by CodeMirror, your code will likely need updates; see PR #6268 for notes. However, the Brackets CSSUtils API remains unchanged.

Node version - The internal copy of Node.js included in Brackets has been upgraded to 0.10.24 (from 0.10.18).

Dialog boxes - The built-in dialog box shown via showModalDialog() no longer has a close button: it can only be dismissed by clicking the main buttons at bottom, or by pressing a shortcut such as Escape. Custom dialogs displayed via showModalDialogUsingTemplate() are unaffected.

New/Improved Extensibility APIs

Preferences - Although new preferences APIs have been added, please continue to use the old APIs for now. The old APIs remain unchanged. The new APIs are still undergoing some flux and will not be ready for wider use until Sprint 37.

Node integration - New, simplified NodeDomain API makes connecting to Node from Brackets code easier and less error-prone. Full docs TBD, but details here in the meantime.

Also, Node-side APIs can now send back binary data to Brackets by returning a Buffer, which will show up on the Brackets side as an ArrayBuffer. Read more.

StatusBar - addIndicator() can now actually be used to add indicators to the status bar (previously it did not do what the name implied, making it less useful). It also has a new optional parameter, insertBefore. If specified, the new statusbar indicator is inserted before the indicator with id of insertBefore. If omitted, the indicator will be inserted at the beginning. (In some previous sprints, the indicator

Known Issues

  • Windows XP issues: Unable to install extensions, run Live Preview, or detect external file changes instantly. Bug 6951.
  • 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.
  • #3207: If you use a Sprint 21 or earlier build after using this build at least once, a few preferences such as Recent Projects may get reset. (You can back up your cache folder if you're concerned about this).
  • #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.

Community contributions to Brackets

Pulling source code from Git

  • A new brackets-shell build is required for this sprint.
  • If you have ever built brackets-shell before, delete the brackets-shell\deps\node folder and any Node-related files in brackets-shell\downloads, then re-run grunt setup (this one-time step is required due to a change in the node executable filename).
  • Some submodules were updated this sprint. Run git submodule update to ensure your source tree is fully up to date.

Bugs fixed in Sprint 36

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

Clone this wiki locally