We didn't add major new user-visible features in Sprint 9. Our main goals for the sprint were similar to the previous sprint - Continue to make progress on the extensibility architecture of Brackets: research, basic architecture and extensibility API:
Architecture / Research
Note: "This is research in a very early stage, however a prototype implementation is checked into the
node-proxy branches in adobe/brackets and adobe/brackets-app repos".
Menus and Keyboard Shortcuts As an extension developer, I want to be able to add custom menus and keyboard shortcuts when my extension is enabled. (Ty, Peter, Randy, Raymond, Jason)
Menus.getMenu()with one of the AppMenuBar constants. Then add a menu item using
theMenu.addMenuItem(), linking it to your Command id. The menu item's label will be the string name you gave the Command when it was created. As a convenience,
addMenuItem()also lets you create a keyboard shortcut for your Command at the same time.
KeyBindingManager.addBinding()directly, linking a shortcut to your Command id.
Enable Unit Tests in extensions (Randy, Jason, Peter):
Where Can Extensions Add UI?
The main area where there is still discussion are the guidelines for the application menus, having a large list of every sub menu available makes finding contextually relevant functionality tricky. On the other hand, hiding and showing menu items depending on filetype hides extensions (and can be jarring if it changes from file to file).
See closed sprint 9 bugs. A few other bugs might have been fixed that weren't tagged.
Here are some things we're planning to do over the next few sprints: