Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Release Notes: Sprint 18

Jump to bottom
njx edited this page Dec 21, 2012 · 17 revisions

This is a draft!

This document will not be finalized until the end of Sprint 18 -- approximately December 20.

Note: this final sprint of the year was largely focused on architectural work preparing for future sprints, so there are fewer new features than usual.

What's New in Sprint 18

Full change logs: brackets and brackets-shell

UI Changes

API Changes

NativeFileSystem

  • requestNativeFileSystem successCallback - https://github.com/adobe/brackets/pull/2158 The successCallback now returns a FileSystem object with a root:DirectoryEntry property. Previously the callback returned the root:DirectoryEntry itself.
  • Replace FileError with NativeFileError (implements DOMError) - https://github.com/adobe/brackets/pull/2318 The latest w3 spec passes specifies that error callbacks pass a DOMError object instead of FileError. FileError.code is replaced with DOMError.name. The deprecated enumeration for FileError types has been replaced with an enumeration in NativeFileError (module: file/NativeFileError). This pull request also fixes some consistency issues with error callbacks
  • Check examples and documentation - https://github.com/adobe/brackets/pull/2063

CodeHintManager

  • registerHintProvider requires mode names and priority - When registering with the CodeHintManager (CHM), CodeHintProviders now must also specify a list of CodeMirror mode names (e.g., "html" or "css") for which they are capable of providing hints, and also an integer priority that is used to decide the order in which the CHM polls providers for a particular mode.
  • CodeHintProvider interface changes - The interface that CHPs are required to implement has been simplified. There are now three required methods:
  1. hasHints, which is used to indicate whether or not a provider is willing to provide hints in a particular editor context, and begins a new hinting session;
  2. getHints, which returns either a list of hints for the editor context associated with the current hinting session, or a deferred object that will eventually resolve to a list of hints, as well as indication of whether the first hint should be selected by default; and
  3. insertHint, which inserts a hint into the editor context associated with the current session, also indicates whether the CHM should subsequently open another hinting session.

CSSUtils - added the getInfoAtPos() new API call which returns a context info object for the given cursor position.

New/Improved Extensibility APIs

ExtensionUtils - the following new API calls were added:

  • addEmbeddedStyleSheet() - Appends a <style> tag to the document's head.
  • addLinkedStyleSheet() - Appends a <link> tag to the document's head.
  • parseLessCode() - Parses LESS code and returns a promise that resolves with plain CSS code.
  • getModulePath() - Returns a path to an extension module.
  • getModuleUrl() - Returns a URL to an extension module.
  • loadFile() - Performs a GET request using a path relative to an extension module.

Also, loadStyleSheet() now supports .less files (using the API calls listed above).

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.
  • Debug > Show Developer Tools opens in a new tab in Chrome, rather than a new window in Brackets.
  • #1283: Text selection highlight sometimes jiggles when horizontally resizing window.
  • 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 since it was downloaded from the Internet (you may not see any error or warning 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 18

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

Clone this wiki locally