Fix brace style in class snippet

Use configured brace style for class snippet.
Merge pull request #97 from TheHippo/patch-1

Fix brace style in class snippet
Grab documentation and put it in the debug output.
Show documentation in separate view.

This will open up a new view in Sublime Text and, as you type a function
name, it'll take a best guess at what you're trying to type and show you
the documentation for that function.

Some notes about this.

1. There's no way to correctly know what the user has selected in the
autocomplete box, as far as I can tell. That's why we have to take a
guess in HaxeShowDocumentation#run.

2. This automatically assumes that any window in the second row of
Sublime Text is the documentation. This is not necessarily true.

3. The first time it opens the window, if you're using some sort of
vi-emulation like Vintage or Vintageous, it'll snap you out of insert
mode. Since it's only the first time (and then never again) I haven't
invested the time to figure this one out. Plus, it's not a big issue.

4. It would be nice to have an option to toggle this off. Currently, if
you don't like it, that's too bad, because if you close it, it'll just
open up again. (Though you can make it as small as you want.)
output documentation to a panel, with hints and Haxe syntax coloring
Fix bug where searching would trigger documentation view.

This is a slight hack, but I can't find any way to directly ask Sublime
if the user's input is currently in a search bar.

I also changed the function from on_selection_modified_async to
on_modified_async, because this function is only called when the user
types in something. Previously, the function would be called even if the
user moved the selection around with the arrow keys without typing.
Fix bug with documentation.

Unfortunately, calling sel() on active_view() will just return the same
object every time, so the comparison I was doing would always fail.
There's no easy way to compare sel() objects - you'd have to loop
through every selection to ensure it's right, and it gets even more
painful to duplicate - so I decided to check if the first region has
changed to see if we're typing in the find window or not.

If the user is actually using multiple selections, it's fine,
since it's hard to say which of the functions they're selecting should
be shown documentation anyways.
Ensure we're in a Haxe file.
Merge pull request #116 from johnfn/master

Fix bug where searching would trigger documentation view.
Adding major haxelib commands to command palette, and making them interactive from Sublime.
Refactor haxelib feaures out of the way for now. Rewrote project system to 1) guess better, 2) read more information, 3) use the build tools to determine all the actual libs included, 4) use the build tools to list all defines and classpaths for code complete 5) use the settings files to specify custom build targets, run commands, and project extensions for guessing. Still wip, there are some issues to resolve but it is coming along nicely.
Making projects work per window, and more consistent. Still a bit more to go before projects are completely working.
typo
Revert 58f2b32..598ff6c

This rolls back to commit 58f2b3217eecb7d9b3b94896686683105a91b488.
removed automatic documentation panel, added shortcut for showing
Revert "Revert 58f2b32..598ff6c"

This reverts commit 35dba61a4f07a816eef1c0583ca75cfe4b41dfaa.
More refactoring

Temporarily moving to the new build settings for quicker testing
Updating generate import command
More refactoring to the Helper class (regex)
Cleaning up for continued refactoring

Moving the project specific refactoring out of this branch
Fixing broken commands for plugin and haxelib features
Fixing macro and keymap changes I had made for testing
Undoing weird side bar additions when messing around
Fixed openfl compatibility
Added support for lime projects