Brackets Blog

code the web

Brackets Weekly Episode 6

If you have trouble watching the video below, make sure you have Flash enabled for www.ccv.adobe.com.

Covered this week:

Keep up with Brackets Weekly via the low-traffic brackets-announce mailing list.

Brackets 0.41 Release (Replace Across Files)

The latest Brackets release is out, introducing a much-requested feature: the ability to replace text across multiple files in one batch.

Replace In Files
The new multi-file Replace In Files works like a blend of the existing Find In Files and single-file Replace commands. Start by selecting Find > Replace In Files (or right-click a folder and select Replace In… to limit the scope):

Using the Replace In Files bar, you can choose which files to search (using the same “exclusion sets” as in Find In Files) and set your search & replacement text (using all the same options as available in the single-file Replace bar). But Brackets doesn’t modify any files yet – first you get an opportunity to review all the matches and filter out ones you don’t want to modify:

Once you’re done, click the Replace button in the panel header to replace all the selected matches. By default, Brackets will leave all these replacements as unsaved changes – so you can Undo if needed. But if more than 20 files are involved, Brackets avoids flooding your workspace with open documents by performing the replacement directly on disk. You’ll always be warned in this case, since such replacements can’t be reverted via Undo:

Note: if you like the bottom panel’s checklist of replacements, you can use it for single-file replace too! Either right-click a file and choose Replace In…, or start a regular single-file Replace and click the “Batch…” button (formerly named “All…”):

Lastly, we took this opportunity to considerably clean up and consolidate our find/replace-related code. This will make further improvements in the future much easier – look for more to come!

Other Changes
Stability improvements – In the past, certain JS files have caused Brackets to freeze or become sluggish while analyzing the file for code hint information. Now, files that take too long to process are automatically ignored (code hints will still show, but they will reflect only what was gleaned from the other files in the project).

Renaming files – There’s now another way to rename files in Brackets: in the file tree, click the selected file a second time to rename it. This is similar to how the Windows Explorer and OS X Finder file views work.

Community Contributions

Summer Break
Lastly, a quick reminder: Adobe members of the Brackets team will be on break the week of June 30 – July 4, so responses to bug reports & pull requests may be delayed.

Brackets Weekly Episode 5

If you have trouble watching the video below, make sure you have Flash enabled for www.ccv.adobe.com.

Covered this week:

New! Keep up with Brackets Weekly via the low-traffic brackets-announce mailing list.

Brackets Weekly Episode 4

If you’re having trouble viewing the video, make sure that Flash is enabled for www.ccv.adobe.com.

There’s a special Friday episode of Brackets Weekly coming this Friday, June 27th.

Links from this week’s show:

Brackets Weekly Episode 3

Some people have reported trouble viewing the videos for Brackets Weekly. If you have trouble with the video below, please try this link and let us know in the comments if that worked for you. Thanks!

In this week’s episode:

Update on the Comp to Code Tool in Brackets

With the launch of Project Parfait in preview, as well as Lee’s open sourcing of his Response tool, I wanted to provide an update on the “Design Comp to Code” tool that we showed last year at Adobe MAX. After a bit of a delay in getting started, we’ve been hard at work turning that vision into a reality as an extension for Brackets. We’ve been able to leverage a lot of work from the Parfait team to bring a comp to code workflow directly into your code editor.

We’re excited about where we’re at now and we’ve recorded a video to share some of the progress we’ve been making. If you’ve seen the MAX video, you’ll see the core features that were in that original vision, as well as some new concepts like code hints for text and generating an asset from multiple layers.

We’ll be doing a private beta of the extension soon and we would love you to be a part of it! If you’re interested in participating, you can fill out the survey here. We’ll be starting small but hope to expand the group fairly quickly after the initial invites.

Over the next couple of months we’ll be sharing more about what features we have planned, so keep an eye on the Brackets blog for updates. We’re looking forward to sharing more of the roadmap and information on the
public preview. Let us know what you think!

=Ryan and the Comp to Code Team
ryan@adobe.com

Brackets Weekly Episode 2

Covered this week:

Brackets 0.40 Release (Find Exclusion Sets)

We’ve shipped a new and improved Brackets! If you don’t see an automatic update notification for it, be sure to manually “Check for Updates” from the Help menu, because there was a bug preventing update notifications from appearing under some circumstances. This bug is fixed in 0.40, so you should be all set after this one.

Exclusion Sets

The biggest improvement in the new release is the ability to manage multiple “exclusion sets”. Previously, you could exclude files and folders from searches. It’s often the case that you need to exclude different files depending on the project you’re working on or even within a single project if you’re searching either the client side code or the server side code, for example. The new Find in Files bar supports that:

 

Exclusion sets in Find in Files

Exclusion sets in Find in Files

 

Why exclude files? Brackets file search has gotten much faster since we introduced caching a few releases back. Even so, if you can reduce the files that Brackets needs to search, you’ll speed up those searches even more. But, more importantly, excluding files you know are not interesting improves your search results and lets you focus on the matches you truly need.

The New UI

Where there used to be a button to modify the list of excluded files, now there’s a drop down menu.

New Exclusion Set… opens up the editing dialog to create a new exclusion set.

Don’t Exclude Files turns off the exclusions and tells Brackets you want to search all files in the project.

Below those two items is a list of your saved exclusion sets. The currently selected one has a checkmark next to it. You can edit any of these previously used sets by hovering over that item and clicking the pencil icon that appears.

Editing Exclusion Sets

Edit Exclusion Set dialog

Edit Exclusion Set dialog

The Edit Exclusion Set dialog lists the wildcards for files you wish to exclude, as it did before. New in this release is the ability to give the set of exclusions a name, making it easier to identify in the menu. Also new is a display of how many files in your project will be searched, giving you an idea of how effective your filter is. In the screenshot above, Brackets will only search 27% of the files in the project (which is Brackets itself). If I remove node_modules from the list of exclusions, I see this:

WithoutNodeModules

I jump to searching 76% of the files in the project. It’s easy to see that I’m saving myself a lot of searching. Even better, this can give me an indication that I may have typed something wrong if the effect on the number of files to search is more or less than I expected. Enter just “*” and you’ll see the number of files to search drop to zero!

API Documentation

Brackets committer Chema Balsas has put together a program for generating Brackets API documentation. He and Randy Edmunds worked together recently to get the docs cleaned up and online. There’s still some room for improvement, but we wanted to spread the word because these docs are already a big win for extension developers. Check out the Command Manager docs, for example, for a details on how commands are added to Brackets.

CommandManager Docs

CommandManager Docs

Community Contributions

Missing Update Notifications for Brackets?

Perhaps you’ve wondered why you haven’t seen an update notification for the last few releases of Brackets. You’ve heard about the new release, but haven’t gotten an update notification yet.

What happened? After we made Brackets Release 39 available, we found out a bug that might prevent the update notification dialog from showing up automatically for a number of users. We believe the bug was introduced in Release 37.

If you are still using an older version of Brackets (version < 39), you can trigger the update check manually by opening the Help menu and clicking “Check for Updates”.  This will show the update notification and direct you to download Release 39. You can also download it directly from brackets.io.

We expect to fix this in Release 40, so if you haven’t been getting the update notifications so far, you’ll need to manually check again in a couple of weeks. Once you’ve installed Release 40, which will be available in the next couple of days, update notifications should start working again at that point.

For everybody else who wants to know the technical details, you can find them in the comments of this bug report.

Sorry for the inconvenience!

 

Brackets Weekly Episode 1

There’s a lot going on around the Brackets project, so I thought it would be useful to make a quick roundup (just 90 seconds) of the new and interesting. Here’s Brackets Weekly episode 1:

Covered this week:

Episode 2 is coming June 9th. Mail tips to dangoor at adobe.