We’re incredibly proud of the momentum that Brackets continues to have. Over 350,000 people are using Brackets every month. There have been 283 contributors to the project and users have installed 890 different extensions. The community has also become even more active in the project over the past couple of months. We’ll soon be releasing Brackets 1.5 which has a number of fixes and enhancements that were contributed by the community.
The Brackets team at Adobe has been spending the past couple of months talking a lot about how we can continue to move the project forward. We all believe that Brackets is the absolute best code editor out there for the web and the success of Brackets has led to some very good discussion about how Adobe can make our commercial tools better, especially our flagship web tool Dreamweaver. We understand that any good web tool needs to have a powerful code editor at its core.
After discussing how we recreate Brackets features in Dreamweaver, we realized it would be more logical to use Brackets as the code editor for Dreamweaver and are going to start working on that plan.
This won’t have any impact on how Adobe will support the open source project. Brackets itself will remain 100% free and open source. Adobe will continue to maintain a strong engineering team on the project and actively engage and support the community. We will also continue to add features to Brackets and as we do the integration work we’ll be adding a number of core features to the open source project. But it will also mean that overall progress may be slow in the short term as the team works on both the integration work and the core product. As performance issues or bugs come up and get fixed while working on the Dreamweaver integration, we plan to fix those in Brackets directly and contribute them back to the open source project.
Once the integration work is done, which should be in the next 6-9 months, the development team will once again be focusing on Brackets. We will continue to add features and improvements to Brackets which will then make their way into Dreamweaver by virtue of the open source project. We will be working directly in the core Brackets codebase, not a fork, so that features and enhancements benefit the community as well as Dreamweaver.
The Adobe team continues to be both humbled and inspired by the way the community contributes to Brackets and moves the project forward. Brackets has always belonged to the community and that community has never been stronger than it is now. We are excited about this new phase because it allows the Adobe team to spend time on Brackets while also making an impact on Adobe’s commercial tools.
Be on the look out for the 1.5 release over the next couple of weeks. It’s a great release with a number of enhancements and fixes, most of which have come directly from community contributors.
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!
The team has been hard at work on the 1.4 release and because it’s taking a little bit longer I wanted to provide a quick update on that release as well as share some of the current thinking from the Adobe engineers about where we’ll be focusing our efforts over the next few releases.
One of things we want to do as a team is plan our work around a specific theme for each release. That helps overall productivity for the team because they’re diving into a specific area of Brackets but we’re also hoping that it makes it easier for the community to contribute by being open about what kinds of pull requests we’re likely to prioritize.
This doesn’t mean that the only things that go into each Brackets release will be part of the theme. The other, non-Adobe committers all have their own priorities and things they want to get in so we’ll still have nice, varied releases.
But on the Adobe side I wanted to share our current thinking. And all of this is subject to change based on continued feedback from all of you as well as the other committers.
We’re also exploring using Waffle a lot more (versus Trello) because so far the team likes how it integrates with Github. So you may see fewer updates to Trello and more information in Waffle as we get our process down.
It’s been a while since we did a performance scrub and we thought this was an ideal time to do it. We’re starting off by trying to measure where we are compared to other editors, then we’re going to see what we can fix, and finally we’re going to make those performance improvements. My hope is that every 6-9 months we could do another round of performance testing and optimization to keep Brackets running fast. We’ve been looking into a few areas:
We felt best about what improvements we could make to Switching between files and Find in Files so we’re taking those for 1.4 and following up on the other items. We’re hoping to release 1.4 in the next couple of weeks.
For release 1.5 we want to make sure that the innovative Brackets features, like Live Preview, and Quick Edit work with modern web technologies like preprocessors and templating engines. We want to make things like Quick Edit work with preprocessor mixins, and also make Quick Hover work with colors and images you’ve defined as variables.
This one is a little bit more broad, but for the 1.6 and 1.7 releases we want to spend a lot of time thinking about what innovative features we can bring to Brackets. Things like Quick Edit and Live Preview that will help web designers and developers code faster. Some of the initial things we’ve brainstormed are CSS optimization tools, Grunt integration, and in-browser design tools. As we get closer to the 1.6 release we’d love feedback and crazy ideas about what Brackets could do to help you.
Our 1.0 release marked the point where we felt like Brackets was really ready for prime time. But there are still some core editor improvements that we’d like to make. Some of the things that might fall into this bucket would be theming the entire UI, allowing multiple Brackets windows, non-UTF files and split view for more than 2 documents. This could also end up being a release where we do some work to improve the UI of the extension manager in Brackets.
I hope this provides a bit of context to what we’re planning and why. But as I said, we’d love to continue to get feedback about whether these themes/features are the right fit and what else might be missing for you in Brackets.
I’m incredibly happy to be able to announce that the Brackets committers are welcoming a new member: Marcel Gerber. Marcel has been a member of the Brackets community for a long time and has been playing a big role recently in doing code reviews, triaging bugs, and generally helping out wherever he can. He’s also going to be our youngest committer by a wide margin! Here’s a bit about Marcel in his own words:
I am a 16-yeared student, currently attending a German “Gymnasium” (similar to high school) focussed on math and science. I am going to graduate in 2017 with an “Abitur”, after which I’d like to study at university. I’m not yet sure on what to study, but I tend to Computer Science.
When I started developing little websites, I used a little-known app called Webocton Scripty, and then, reading through some random forum thread, I heard of Brackets the first time. I downloaded it, still in an early phase (it was like Sprint 20 or something), but I enjoyed using it.
On a personal note, I enjoy skiing and waterskiing a lot, and also just hanging out with my friends and doing stuff together.
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
The Brackets community has grown by leaps and bounds over the past year, especially after our 1.0 milestone last fall. Earlier in the development of Brackets we felt more confident guiding the project based on direct user feedback and our own intuition. But as the project has grown, we need a better picture of how people are using Brackets so we can continue making it even more awesome. Rather than relying on guesswork, we think the best approach now is to gather real usage data.
Media discussions often focus on gathering data for the purpose of selling ads, but it can also be immensely valuable simply for making your app better. Knowing how people use an app helps decide what to build, prioritize when to build it, spot usability/discoverability problems, and find lurking bugs and reliability issues. Without those insights, we – and our community of extension authors – are flying half blind.
So to serve all our users better, Brackets 1.3 will introduce a new Health Report feature that we’ll use to guide future development. But Brackets isn’t just any app – it’s open-source, and for a developer tool we realize privacy must be the absolute #1 priority. The Health Report will be:
On the topic of transparency, we want to start by sharing some of the more limited information we already have available without Health Report. This Google spreadsheet tells the story of how Brackets grew from an early preview in the spring of 2012 into a vibrant, thriving project with nearly 600 extensions, 120 themes, and over 250 contributors to the core code. Be sure to check out the tabs at the bottom for visualizations like the ones shown below.
We scrape together this information from a variety of sources today, but all of them have significant limitations:
Downloads – we can just count how many times people clicked the Download links on brackets.io. This may undercount Linux, where some users get Brackets from unofficial sources like Linux app repositories – we hope Health Report will give a more accurate picture of how many Linux users love Brackets!
Users per day – we can get a rough picture of how many people have used Brackets in a given day by counting how many hits the update JSON feed gets, since Brackets checks for updates exactly every 24 hours. But this is impossible to aggregate into measures like weekly or monthly active usage; again, Health Report will give a more accurate picture.
Extensions & themes – the Brackets extension registry makes it easy to see how many extensions are currently available.
Extension downloads – the extension registry knows how many times each extension package has been downloaded. But this is very rough, since it lumps together new “installs” of an extension with upgrades of an existing extension; extensions that are updated more frequently will have much higher download totals. Health Report will show how many users installed an extension and kept it installed. With more reliable data, we can begin exposing download counts in the Extensions Manager UI.
Contributions to core code – git history makes it easy to see how many pull requests we’ve merged from community contributors.
The initial version of the Health Report will only add a few new pieces of key data. It works by sending a short report once every 24 hours, containing:
That last item highlights an important point: the Health Report isn’t just for core Brackets developers – we also want this data to help extension authors. This initial version of the Health Report will give authors a much clearer picture of how many people benefit from their extensions.
In the future, we’d like to carefully expand the Health Report to include other useful information. We’ll be sure to announce any changes ahead of time, and we’d love to hear feedback on what other information would be valuable for you to see.
Because we’re building this feature for the benefit of all Brackets community members, please let us know your thoughts by commenting below.
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!
Music is what keeps me going and in my free time you can find me playing Keyboard
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!