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.
Some of you are familiar with the Extract for Brackets extension, a tool used to work with PSDs shared via Creative Cloud. As announced in this post on the Creative Cloud blog today, we are discontinuing the extension effective on June 28 due to low usage. Please note that any PSD files you’ve used with Extract will still be available to access or share within the Creative Cloud Assets service.
To continue using Extract functionality, we suggest checking out the Extract panel in Dreamweaver CC. Thank you for your feedback and support during this process.
And here’s some more about Swagatam in his own words:
I am a software developer by profession. Started carrier as a Data warehouse and Business Intelligence analyst and then moved on to server side programming in Java. After a few years I started embedded programming for Set top boxes and followed it for a while.
I got introduced to web technologies and open source in 2014 and eventually it was Brackets to start with. I really love Brackets for its simplicity and extendibility. Got hooked onto web technologies ever since and to learn DOM manipulation and styling developed an extension “html-designer” on Brackets for designing web pages/applications using HTML/CSS.
Apart from Computers, I love automobiles and photography.
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:
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.