We’re back with another exciting update for Brackets! Here’s a quick summary of all the features in Brackets 1.13
Organize Files/Folders in File Tree
Open Remote Files
Download it here.
You can now intelligently rename functions and variables with scope awareness. You can select a piece of code and create a Try/Catch block for it. Convert anonymous expression/function block to an arrow expression in a click. Create Get/Set functions for the selected identifier in context of a class/construct. You can now extract an expression as a variable in the current scope.
Selected code blocks can be extracted as a function in a selectable scope chain with Brackets taking care of dependency symbols parameterization.
Happy Coding !!!
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 are excited to introduce the newest committers to the Brackets community. I will let them introduce themselves.
Hey guys, I joined the Adobe Dreamweaver team as a Software Developer this summer, straight out of college. But my relationship with Brackets started way before that. I was lucky to grab an internship at Adobe during the first half of this year.
As an individual, I am passionate about developing things that affect the users directly, and things that provide a creative outlet. I am also an avid reader and sometimes dabble with writing. I am really excited to start this new journey, and hope to learn new stuff.
I am really passionate about learning new Technologies. I am currently working with the Dreamweaver team.
Apart from computers I love Bikes, Road-trips
I am really passionate about solving computational and analytical problems. I am currently working with the Dreamweaver team.
I have also worked in the frontend team at housing.com where I made a 360 degree virtual tour of a house, in which I was introduced to technologies like WebGL(Three.js), CoffeeScript and Webpack.
I started using brackets 5 months back and since then I have loved it for its simplicity, intuitive UI and extensibility.
Please join me in welcoming all the newest committers.
Developers love Brackets and we are committed to making Brackets the best coding editing experience.
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.
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.
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.
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.
Music is what keeps me going and in my free time you can find me playing Keyboard