Mirrors/brackets
1
0
Fork 0
mirror of https://github.com/adobe/brackets.git synced 2024-11-20 18:02:54 +01:00
Code Issues Releases Activity
Mirror of https://github.com/adobe/brackets https://blog.brackets.io/
10,710 Commits 178 Branches 114 Tags 128 MiB
JavaScript 77.1%
HTML 12.4%
CSS 8%
Less 2.1%
PHP 0.2%
5fb442db44
Go to file
Jason San Jose 5fb442db44 minor readme update Live Development -> Live Preview
2013-11-13 15:56:17 -08:00
samples Spanish strings sprint34 review 2013-11-13 01:18:25 +01:00
src Merge pull request #5941 from adobe/randy/issue-5933-2 2013-11-13 14:45:53 -08:00
tasks fix test-integration task on linux 2013-09-17 15:21:48 -07:00
test Modify the FileSystemEntry.exists callback to take an additional error parameter. 2013-11-12 14:10:14 -08:00
tools updating hacking scripts to remove 'Sprint' suffix from app folder 2013-10-30 21:40:36 -05:00
.gitattributes Normalized Line Endings and added .gitattributes 2013-02-02 21:29:11 +01:00
.gitignore Add Request tests to gitignore so that they're not automatically 2013-10-18 08:17:33 -04:00
.gitmodules Remove old smart-auto-complete submodule. Check in latest version from upstream repo (as local files). Point Brackets at new version. NOTE that this commit breaks Quick Open, but I wanted to keep this commit at the exact version from the original repo--the next commit will fix Quick Open. 2013-11-06 10:54:13 -08:00
.jshintrc Add grunt tasks for jshint and jasmine. Refactor and move package.json, replace existing with config.json. Add Travis-CI support. 2013-01-24 10:45:28 -08:00
.travis.yml Tell Travis to use Node 0.10 2013-09-23 21:34:07 -04:00
CONTRIBUTING.md Code review & other tweaks to .md cleanups: 2013-05-17 15:13:52 -07:00
Gruntfile.js Turn off jasmine-node again, due to intermittent failures 2013-10-25 10:27:20 -04:00
LICENSE Changed license to be MIT 2012-09-21 00:31:09 +02:00
NOTICE Updated NOTICE file for Sprint 33 2013-10-29 21:17:05 -07:00
package.json set Sprint 34 2013-11-01 15:15:54 -05:00
README.md minor readme update Live Development -> Live Preview 2013-11-13 15:56:17 -08:00

README.md

Welcome to Brackets! Build Status

This is an early version of Brackets, a code editor for HTML, CSS and JavaScript that's built in HTML, CSS and JavaScript.

What makes Brackets different from other web code editors?

  • Tools shouldn't get in your way. Instead of cluttering up your coding environment with lots of panels and icons, the Quick Edit UI in Brackets puts context-specific code and tools inline.
  • Brackets is in sync with your browser. With Live Preview, Brackets works directly with your browser to push code edits instantly and jump back and forth between your real source code and the browser view.
  • Do it yourself. Because Brackets is open source, and built with HTML, CSS and JavaScript, you can help build the best code editor for the web.

You can see some screenshots of Brackets on the wiki, intro videos on YouTube, and news on the Brackets blog.

How to install and run Brackets

Brackets isn't ready for general use yet.

Some of the features you would expect in a code editor are missing, and some existing features might be incomplete or not as useful as you'd want. That said, what's there is reasonably stable—the Brackets team uses Brackets to develop Brackets full time. So feel free to give it a spin and let us know what's missing!

Download

Installers for the latest stable build for Mac, Windows and Linux (Debian/Ubuntu) can be downloaded here.

The Linux version has most of the features of the Mac and Windows versions, but is still missing a few things. See the Linux wiki page for a list of known issues and to find out how you can help.

Usage

By default, Brackets opens a folder containing some simple "Getting Started" content. You can choose a different folder to edit using File > Open Folder.

Most of Brackets should be pretty self-explanatory, but for information on how to use its unique features, like Quick Edit and Live Preview, please read How to Use Brackets. Also, see the release notes for a list of new features and known issues in each build.

In addition to the core features built into Brackets, there is a large and growing community of developers building extensions that add all sorts of useful functionality. See the Brackets Extension Registry for a list of available extensions. For installation instructions, see the extensions wiki page.

Need help?

Having problems starting Brackets the first time, or not sure how to use brackets? Please review Troubleshooting, which helps you to fix common problems and find extra help if needed.

Helping Brackets

I found a bug!

If you found a repeatable bug, and troubleshooting tips didn't help, then be sure to search existing issues first. Include steps to consistently reproduce the problem, actual vs. expected results, screenshots, and your OS and Brackets version number. Disable all extensions to verify the issue is a core Brackets bug. Read more guidelines for filing good bugs.

I have a new suggestion, but don't know how to program!

For feature requests please first check our Trello board to see if it's already there; you can upvote it if so. If not, feel free to file it as an issue as above; we'll move it to the feature backlog for you.

I want to help with the code!

Awesome! There are lots of ways you can help. First read CONTRIBUTING.md, then learn how to pull the repo and hack on Brackets.

The text editor inside Brackets is based on CodeMirror—thanks to Marijn for taking our pull requests, implementing feature requests and fixing bugs! See Notes on CodeMirror for info on how we're using CodeMirror.

Although Brackets is built in HTML/CSS/JS, it currently runs as a desktop application in a thin native shell, so that it can access your local files. (If you just try to open the index.html file in a browser, it won't work yet.) The native shell for Brackets lives in a separate repo, adobe/brackets-shell.

I want to keep track of how Brackets is doing!

Not sure you needed the exclamation point there, but we like your enthusiasm.

What's Brackets working on next?

  • In our feature backlog, the columns labeled "Sprint N" are features already in progress and should ship within 2 weeks. Features at the top of the "Product Backlog" list will come next.
  • Watch our GitHub activity stream.

Contact info