
When you open or create a Markdown file in Brackets, it splits the screen horizontally into two panels – one for editing, and one for a live preview. If you work with Markdown, you might find the Markdown Preview extension to be useful. It probably warrants its own article, so I won’t cover it in detail here. Theseus is a JavaScript debugger for Brackets, which works with both Chrome and Node.js.
BRACKETS FOR MAC REVIEW CODE
If you’re looking for features found in other code editors, there are extensions for code-folding, snippets, and smart highlighting, among others.
BRACKETS FOR MAC REVIEW INSTALL
Simply click the “brick” icon on the top right, then you can search for and install them from within the application. The process of installing an extension couldn’t be easier. I’m going to take a look at a few that stood out for me. There are already a significant number of extensions available. The true power of Brackets, I feel, lies in its potential for extension.

For example, when writing SASS it would be good if, once you start typing out a nested selector (i.e., with a period or a hash) that code completion would stop prompting you for a rule. I’ve found a number of editors in the past to feel sluggish, which negatively impacts the experience, but not so here. Other FeaturesĪs you’d expect from a code editor, Brackets implements code completion. However, the performance impact of doing it any other way would probably create its own problems. JSLintĮnabled by default, built-in JSLint support will check your Javascript code upon saving, with its results displayed as a panel below the main editing window.īecause Brackets runs the JSLint process when you save, rather than as you go, it can feel a little unresponsive you can correct something and the report remains on-screen because you haven’t saved it. It will be interesting to see what’s produced there are clearly many possibilities for it. It looks like third-party extensions will provide additional contexts for Quick Edit, like the regular expression editor described later in the article. Again, it’s best illustrated with a screenshot: While unlikely to be used nearly as often as the CSS rule or color editor, the bezier curve editor is a hugely impressive little feature. Also, the same keyboard shortcut ( Ctrl / Command + E) gives you a pretty sophisticated color selector / converter, as illustrated below. Hovering over a color in a CSS declaration shows a small swatch of that color. This is probably best illustrated with the following screenshot. When you’re editing HTML, if you click a tag with a corresponding CSS declaration situated in a linked file and hit Ctrl / Command + E, an inline editor appears allowing you to quickly edit that rule. The Quick Edit feature is context-specific. If you’re editing a CSS file used by the currently visible page, highlighting rules causes the preview to highlight elements which are affected by them. If you make a change to a linked CSS file which impacts the current page, that too gets reflected immediately in the browser. It doesn’t just work with HTML files, either.


It’s a truly great feature, particularly if you have a splt-screen setup. It’s essentially Chrome’s Web Inspector, but with all the benefits of a self-contained editor.
BRACKETS FOR MAC REVIEW MANUAL
The Live Preview feature launches a new Chrome window showing the current page that not only doesn’t require a manual refresh when you change a file, but also as you type. Let’s look at some of the key features of Brackets.
