Fix #48 - Evaluation Delimiter token is added
Merge branches 'delim' and 'master'
Tuned coloring of the evaluation result
Fix #53 - Automatically evaluate worksheet on creation

At worksheet creation, the document is now immediately evaluated. A valuable
side-effect of doing so is that the resident compiler is then immediately
available.
Use a VM from the platform

The evaluation is done by the VM configured with the project.
Fix #22
Fix #57, Fix #58 - Stop evaluation on editor's  `dispose`

The current solution seem to be working, but it's not thread-safe (meaning
that it is still possible to get a NPE, just very unlikely). That said, the code
is robust enough and can recover from it, i.e., the worksheet will still be
functional even if a NPE is thrown.

I've added a big comment on the reason why the current solution is not
thread-safe, we'll have to see how to fix this.
Renamed `ProgramExecutorService` to `ProgramExecutor`
Corrected implementation of `using`

The former implementation used to re-throw all exceptions, while
the intention was to swallow some of them (i.e., ``swallowException``).
Ran "organize imports" on all sources
Fix #40 - Worksheet can now be compiled against both Scala 2.9 and 2.10

Update sites are (both for Scala IDE V2.1):

* http://scala-ide.dreamhosters.com/nightly-update-worksheet-scalaide21-210/site/ (for Scala 2.10)
* http://scala-ide.dreamhosters.com/nightly-update-worksheet-scalaide21-29/site/ (for Scala 2.9)
Fix #25 - Caret is kept at the same position after evaluation

* Empty lines are no longer stripped, the reasons are:
    + Keep correct indentation of empty lines.
    + Correct handling of caret position (i.e., if the caret is
      in the middle of an empty line, it should stay there after
      evaluation).
* The new caret position can never be after the old caret position
  (this should motivate the change in Mixer.scala)

This fixes the issue with correctly updating the caret position in
most of the situations, but not all of them. Honestly, I don't think
we should spend more time with trying to improve this, because messing
with the user's document is just wrong. Instead, we should split the
editor into two views: a left one used by the user to write code, and
a right to show the evaluation result (#70).
Merge pull request #69 from dotta/issue/25-handle-caret-position

Fix #25 - Caret is kept at the same position after evaluation
Don't require a specific version for Eclipse dependencies.
Don't set the preference store. Re-enables red underlines. Fix #55.
Remove useless @inline annotations.
Show build errors properly. Fixed marker positions and magically error markers appear in the editor.

This solution is only halfway: the full line is highlighted as an error. We don't have a precise way to 
map between instrumented and uninstrumented positions. We assume no newlines are added by the instrumenter,
and use only the line number information.

Fix #73.
Let the user navigate during the mixing phase.
Strip the source before compilation/evaluation. If there are errors, there's no results left, and also the user gets a chance to see that something is happening when the evaluation results don't change.
Stop evaluation on backspace and delete as well as any printable character.
Update to the latest Scala IDE binaries (ScalaDamageRepairer was removed).