Sublime text 3 rewrite and new features

[sentience]

Hi @iamruinous et al,

I spent my weekend at Rails Camp 17 just north of Sydney, Australia re-writing this package for Sublime Text 3, making it generally easier on the eye and adding a number of additional features. This pull request is the culmination of that work.

Here’s a glance at what it looks like:

An overview of the changes:

• No longer depends on simplecov-sublime-ruby-coverage formatter. Instead uses the simplecov-json gem, which Atom’s SimpleCov integration uses as well.
• Coverage is now displayed only when the user requests it, using the Toggle Coverage Highlight command. This display now highlights lines in green and red, with shades of green to indicate the level of coverage. Optionally, the view auto-scrolls to the first uncovered line in the file when highlighting is turned on.
• Current line and whole file coverage statistics are displayed in the editor’s status bar, and are updated in response to cursor movements.
• A new Show Project Coverage command displays coverage levels for all project files, from least covered to most covered, with an attractive, color-coded bar graph.
• This package now requires Sublime Text 3.

This is a full rewrite. Essentially nothing of the original code survives.

Since the rewrite I am contributing here works only on Sublime Text 3, my plan would be to publish a Package Control manifest keeping the previous version of the package (with maintenance to happen as required on a branch) available for ST2 users, and making the new version available for ST3 users.

Given that this package has not been updated in over two years, I am operating under the assumption that it is no longer being actively maintained. I would like to volunteer to take over active maintenance of and support for this package. I’m happy just to be added as a contributor to the intergrum/SublimeRubyCoverage repository for now so that I can handle the release of this new version, but in time (assuming Integrum will no longer be maintaining this package) I think it would make sense to move it over to my GitHub account (with the appropriate repository move added to Package Control, so users are auto-upgraded).

Please do not simply merge this to master, since it will break the package for current ST2 users who are using it. Rather, let me know if you’re happy to add me as a maintainer, and I’ll take care of performing an orderly release of the new version while keeping the old version available for ST2 users.

I look forward to hearing from you! 😄

[sentience]

As I have not heard back on this, I will submit my package to Package Control separately.

[iamruinous]

This is awesome!

We aren't maintaining this anymore, so I'm happy to see someone else take over.