We’re delighted to announce Brackets 1.9 release, an update that is packed with features! As we’d mentioned some time ago, we’re focused on innovating and delivering regular updates to Brackets.
Download the latest version here.
In this update, you can take advantage of:
Most modern-day web developers work with a multi-monitor set-up, where they’re writing code on one and previewing design changes real-time on a browser, on another screen. Connecting these 2 distinct operations is essential to a boost productivity of a developer. With Reverse Inspect, a developer can now quickly inspect his code by clicking on elements in the browser and have corresponding chunks of code highlighted inside of Brackets.
Along with the Batch option to selectively replace, you can now use the Replace-all function to replace all search results at once.
The Brackets Extension Manager now displays download count for listed extensions. And also, the Extensions can now be sorted based on download count or published date in ‘Available’ and ‘Themes’ tab.
You can now change language mode for Untitled Documents. To its end, Brackets provides Code Colors and Hints based on the language mode that is selected for an untitled document.
GitHub Organizations can now publish and own Brackets extensions. All public owners who’re part of the organization can update extensions.
See the complete list of fixes and enhancements in this version.
We just released Brackets 1.8. Download it from here. Brackets has gained incredible momentum in the last few months. Almost 800,000 people are now using Brackets every month. Our contributors have played a major role in making sure it evolves as the leading code editor for web developers.
The current version has a big list of contributions from our community. Special thanks to Martin Zagora for updating the Node version to 6.3.1.
You can see the complete list of fixes and enhancements on the wiki.
The Brackets team at Adobe had been focussing on bringing in Brackets as the code engine within Dreamweaver during the last 9 months. The team has done an incredible job and it’s being appreciated by the Dreamweaver users. Now that the job is done, we are back with the intent to innovate on features that the Brackets community would love. I cannot wait to announce our 1.9 feature set.
The team just released Brackets 1.7, so head over to brackets.io to download it! As we mentioned, last year, the team has been busy working on integrating Brackets as the core code experience inside Dreamweaver, and that’s resulted in some nice features this release for Brackets users:
If you’re interested in checking out the new, revamped Dreamweaver with Brackets integration, the team is going to be rolling out a public beta very soon. So keep an eye out for that!
Also, this is going to be my last blog post as the Brackets product manager. I’m turning the reins over to the fantastic Brian Thomas who is leading all of Adobe’s web tools. It’s been a pleasure to be part of the Brackets project for so long and I know Brackets is in the great hands of a passionate engineering team and PM.
As of today, Brackets 1.5 is available for download. As we mentioned last week, the Adobe engineers on Brackets are working on bringing Brackets into Dreamweaver as the code surface and we expect progress on the open source project to be slower as that happens. But we still hope to do regular releases and our community is fantastic so a lot of the work that will be in those releases will be community driven. Brackets 1.5 is a great example of that.
This version of Brackets adds the ability to fold selected text via code folding and includes some major performance enhancements to searching. Brackets now also gives you CSS code hints inside of
style tags in PHP documents and we’ve improved the code hinting performance in minified files.
We also fixed a couple of issues with El Capitan and a freezing/crashing bug. You can see the full list of fixes and enhancements on the wiki.
And a big thank you goes out to everyone who contributed to this release:
Today we are releasing Brackets 1.4, that has some great features which include, the new instant search, better preferences editability to name a few.
Say hello to instant search! Searching across files in Brackets has never been this fast. We have worked ground up to improve the performance of find in files inside Brackets. The end result was so good that we now update the search results as you type. This is a great improvement on top of the existing find in files.
Editing preferences is now much easier in Brackets. All the preferences names appear as code hints, while editing the user preferences file. Thanks to the major effort by Amin Ullah Khan, who is the author of this feature. Also,
Debug->Open Preferences File.. will now open up split view and bring up user preferences file
brackets.json in one pane and all the default preferences in other pane.
You now have the option to enable/disable individual extensions from Extension Manager. Thanks to Arzhan “kai” Kinzhalin for his contributions on this.
We have updated our editor’s font (Source Code Pro), which brings in improved support for Greek and Cyrillic character sets.
We have enabled sub-pixel anti-aliasing on Mac by default, that renders the text crisper. This can be overridden by setting the
fonts.fontSmoothing preference to
antialiased, which brings back the old gray scale anti-aliasing.
As always, a huge thanks to our contributors for this release:
Thanks to you for choosing Brackets. We now have over 270,000 monthly active users!
We’re very happy to announce that Brackets 1.3 is available as of today with some great new features and the first implementation of the Brackets Health Report which will go a long way towards helping us improve Brackets and providing extension authors with helpful information about how you all are using Brackets.
One of the most requested Brackets features has been to allow launching it from the command line. As of 1.3, that’s possible! On Windows, when you install Brackets, you’ll be given the option to add Brackets to the right click context menu as well as adding Brackets to your PATH. On Mac, you can install the command line tools by going to File->Install Command Line Shortcut.
Once you’ve done that, you should be able to launch Brackets from the terminal (on Mac) or command prompt (on Windows) with the
brackets command. Following
brackets with the name of a file or folder will open that file/folder in Brackets. You can get more information, as well as troubleshooting info, on the Command Line Tools wiki page.
Thanks to the major effort by Patrick Oladimeji, the original author of the Brackets Code Folding extension, we’ve brought the feature into core so now every user has access to code folding without the need for an extension.
The core feature works the same way as the original extension and now the preferences have been brought into the core preferences system and you can see how to set them on the preferences page.
Thanks again to Patrick for his help on the feature and his enthusiasm for getting it into core.
As I mentioned, this release of Brackets includes the start of our Brackets Health Data collection. As Peter Flynn mentioned in the blog post, the goal is to collect anonymous, aggregated data with an eye on improving Brackets as well as providing more information to the community about how people are using Brackets.
You can opt out any time, as well as see what data we’re sending, by going to Help->Health Report.
This release also fixes a nasty bug on Windows that affected the scroll behavior. We also now highlight Angular templates correctly as plain HTML and we’ve improved our indenting behavior. You can see the full list of fixes over on the Release Notes page.
As always, a huge thanks to our contributors for this release:
APP_NAMEplaceholder instead of “Brackets” in more strings by Pavel Dvo?ák
Brackets 1.2 is out and has a bunch of really fantastic features that users have been asking for for a while. Between a longer than usual winter break for Adobe and ramping up new team members, and fixing some last minute Linux issues, this release took a bit longer than expected, but we hope you enjoy it!
A couple of things you’ll immediately see are that we now offer CSS color name code hints thanks to Marcel Gerber so when you type the
color property in CSS you’ll see a list of W3C color names with a swatch. Marcel also added syntax highlighting for the Dart language so when you open a Dart file you should see things highlighted correctly. This release also makes working with SVG files easier thanks to the SVG code hints that were added by Amin Ullah Khan. Just open up an SVG file, start typing, and you’ll see code hints for tags and properties. A couple of other things from the team include scrollbar tick marks that sill show the location of find/replace matches and make it easy to jump to them. We added common named keys like PageUp, PageDown, Home, etc, to the key binding list so that you can use those names in your custom key bindings or extensions. Finally, Brackets now looks great on Windows High-DPI screens. One of the things we’re most excited about is that we’ve got an initial implementation of moving selected text via drag and drop thanks again to Marcel Gerber. We have a couple of small things we want to fix before it goes on by default, but you can start using the feature now by adding the
dragDropText property to your
brackets.json preference file (Debug->Open Preferences File). It doesn’t exist by default so you’ll have to add this entire line to the bottom of your file (make sure to add a comma to the line above it so it stays a valid JSON file):
The community really, really stepped up on this release and you can see all of the fixes, features, and translations that were contributed in the full release notes.
We’re going to get cranking on the 1.3 release right away. One of the major things we’ll be doing is finally starting to work on the Health Data report proposal. So we can share information about how people are using Brackets and where people are seeing issues that we need to address. I’ll be sharing more information about that over the next couple of weeks.
Thanks again to the entire Brackets community. Happy Coding!
On the heels of the 1.0 release we’re very excited to announce the availability of Brackets 1.1 and an update to the Extract for Brackets extension today. The Brackets team is thrilled with the response we had to the 1.0 launch. Brackets 1.0 was downloaded almost 400,000 times in the past 5 weeks. That’s a humbling number and we are looking forward to keeping up the momentum.
The 1.1 release is primarily a release about stability and making sure we continue to have a good foundation. We updated the version of the Chromium Embedded Framework (CEF) we’re using so that we are now working with a more updated version of Chrome. That means we’ve addressed some bug fixes and users on Windows will now have high DPI support. We also did some work to improve the typing performance with code hints.
As of this version of Brackets you can now define file-type specific preferences by using the language group in your
brackets.json file. You can find out more here. You can now also selectively enable specific linters per project by using the
.brackets.json file in the root of your file.
One of the biggest features in this new version of Brackets is experimental support for the next iteration Live Preview which lets you use Live Preview with browsers other than Chrome. This feature was one that the Intel Brackets committers including Sebastian Salvucci and Arzhan Kinzhalin worked hard on and helped us land for this release. Our hope is to make this the default implementation of Live Preview.
To try out the cross-browser Live Preview, you need to enable a preference in your
"livedev.multibrowser": trueinside of the curly braces on a new line (make sure to add a comma above it if you add it to the end)
Definitely try it out and give us feedback on the new implementation and file any issues you run into.
In addition to Brackets 1.1, we’re releasing an update to the Extract for Brackets extension that includes a new getting started experience and a feature that lets you collaborate with a designer who is using the Creative Cloud. You’ll now be able to open a publicly shared Creative Cloud link right from Brackets.
We’ve revamped the initial experience when you launch Extract for Brackets to walk you through how the product works. If you’ve already tried Extract for Brackets but were a bit confused about how to get started you can click the question mark button in the toolbar. You’ll see new tool tips that will take you through how to use Extract for Brackets.
This version of Extract for Brackets also has a feature that makes it easier to collaborate with designers who are already using the Creative Cloud to store their PSDs. If you’re working with a designer they can send you a publicly shared link to a PSD in the Creative Cloud and all you have to do is paste that URL into Brackets and you’ll be able to extract from that PSD.
You can give it a try by copying and pasting this URL:
http://adobe.ly/1E67WAS into the updated version of Extract for Brackets.
The entire team is excited about both of these releases and building off of the great 1.0 release. A huge thank you to all of our committers and everyone who has filed issues, submitted pull request, and keeps using Brackets. You can see a full list of Brackets changes including community contributions here.
1.0, we did it! This is a big milestone for the Brackets project. Right now you can grab version 1.0 of Brackets, as well as a preview of Extract for Brackets, an extension that Adobe has been working on. Extract for Brackets (Preview) speeds up the process of pulling design information like colors, fonts, and measurement info out of a PSD and turning it into clean, minimal CSS.
When we first started Brackets we wanted to release early and often. We did both. This will mark the 45th release of Brackets in 3 years. In those early releases we acknowledged that there were a number of features Brackets was missing so we warned that it was still early and not necessarily ready for every day use. But in the past 3 years we’ve been very busy adding features to help make Brackets a world class text-editor. Declaring this release as 1.0 is our way of telling the world that Brackets is ready.
We’ve been busy over the last few releases adding a number of major features. If you haven’t looked at Brackets in a while, now is a great time to see the awesome stuff we’ve been working on. We’ve added multiple cursors, split view, theme support, and many more fixes and enhancements. This release includes support for custom key bindings so you can change the shortcut key combinations that Brackets uses. This wiki page describes how to customize them and includes example key bindings that align Brackets’ keyboard shortcuts with the ones you might be used to in Sublime Text.
In addition to Brackets 1.0 we’re also releasing a preview of Extract for Brackets. Extract for Brackets is a Creative Cloud service that lets you view and get information and assets out of a PSD right from your text
editor. Extract for Brackets lets you pull out things like colors, fonts, measurement, gradients, and more from a PSD in the form of contextual code hints in CSS and HTML files. You can also extract layers as images, use information from the PSD to define preprocessor variables, and easily get dimensions between objects. We’re excited about how this will improve the process of moving from design to development and speed up workflow. You can either download Extract for Brackets (Preview) as a standalone extension on the Brackets Extension Registry or included with Brackets 1.0 in a bundle that’s available for download on brackets.io.
While we’re very excited about 1.0, we are also treating this like any other release, so we’ll continue to release often and will be doing the next Brackets release in 3-4 weeks. As mentioned in this blog post we are going to be slightly changing the things that the Adobe team works on. We think there is an unmet need for a coding tool that supports design and we think that Adobe has a lot of expertise in that area. We will continue to work on core features and to support the community’s work on Brackets, but we also want to build the perfect editor for web designers and front end developers that are creating or implementing designs in code. Some of the things we’re going to be working on are improving our preprocessor support, making SVG editing more powerful, and adding more visual inline editors.
Since putting Brackets up on GitHub 3 years ago we’ve seen a great deal of momentum, largely thanks to our community. Our releases regularly see over 100,000 downloads, there have been 245 people who have contributed code directly to Brackets, and we¹re currently the 16th most starred project on GitHub with 18,566 stars. Those are humbling numbers and we’re excited to be working with all of you on making Brackets a success. We’ve also seen over 400 extensions and over 75 themes created in that time, all of which grow the reach and feature set of Brackets. To those of you who have taken the time to write extensions, contribute code, file issues, or even just try out Brackets, we want to say thanks. We couldn’t have done this without you and we are looking forward to continuing to move Brackets forward with you!
Split view has been one of our most requested features for Brackets and with Release 0.44 it’s finally landed. In this release we’ve also overhauled the file tree which should make it more robust. You can see the full list of enhancements here and grab the release here.
With release 0.44 you can now view two documents side-by-side in either horizontal view or vertical view. To enable split view, use the icon and then decide between a vertical split or a horizontal split. Then select the panel you want to open the file in and double-click the file to open it in that pane. You’ll now see two working sets, one for each pane.
We rewrote our file tree to use React which will make it much easier to maintain going forward. During the upgrade we also fixed an issue that wouldn’t let users right-click on files that Brackets doesn’t support.
As of this release you can now use Quick Docs when you’re on a browser-prefixed CSS property. We’ve also fixed two important issues with editing CSS code: one where Brackets stopped working when using Live Preview if you placed your cursor on a non-indented } character inside a comment, and one where the inline editor was blank if your CSS rule contained a vendor-prefixed property that used rgb() color values.
The entire team is excited about this release. We hope you enjoy split view as well as all the other features and fixes that went into this release. And as always, we appreciate those of you who have contributed translations and fixes this release. Here’s the complete list:
cubic-bezier()by Marcel Gerber
!importantby Miguel Castillo
i18nfield by Denisov21