Over a million developers have joined DZone.

Using Topcoat and Brackets? Check Out These Snippets

DZone's Guide to

Using Topcoat and Brackets? Check Out These Snippets

· Web Dev Zone ·
Free Resource

Learn how error monitoring with Sentry closes the gap between the product team and your customers. With Sentry, you can focus on what you do best: building and scaling software that makes your users’ lives better.

I'm a huge fan of the Snippets extension for Brackets. As my memory seems to be getting worse with old age, I find that having a quick way to include code bits into my document is a huge time saver. As an example, I've never been able to remember the right syntax for the link tag for CSS. Ditto for the stupid argument you have to add to form tags for file uploads. I've got some weird mental block for some reason and just rely on my snippets to help me remember.

In that vein, today I whipped up a set of data files for Topcoat, an open source UI framework for desktop and mobile sites. These data files can be added to your Snippets data directory (this will be under your Bracket's Extensions folder and inside of the folder created for the Snippets extension) to provide quick access to the various UI controls Topcoat supports.

Here's a screenshot. Note: I don't usually keep the Snippets panel quite this large.

Hopefully that's readable. I don't typically use the keyboard shortcuts so I didn't really spend a lot of time thinking about them. You can find the bits up on GitHub: https://github.com/topcoat/topcoat-brackets-extension. Any suggestions or pull requests are definitely welcome.

Just to be clear, this code is not an extension itself. That may come in the future.

What’s the best way to boost the efficiency of your product team and ship with confidence? Check out this ebook to learn how Sentry's real-time error monitoring helps developers stay in their workflow to fix bugs before the user even knows there’s a problem.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}