Remove superseded SelectionMover.countStepsToPosition
Use cached-based conversion rather than SelectionMover.move
Remove superseded SelectionMover.isPositionWalkable
Adjust StepsTranslator behaviour

When the requested number of steps passed to convertStepsToDomPoint is
beyond the document end in, or before the start of the document, an
exception will be thrown. This closes a slight hole where asking for a
step beyond the document would return a non-step position. It also makes
the invalid usage of the interface more obvious.
Reducing usages of SelectionMover.countSteps

SelectionMover.countSteps has been replaced by step iterators and other
more performant solutions.
Remove last usages of OdtCursor.move from tests

All remaining OdtCursor tests are really testing other parts of the system that
are already covered in their own unit tests. For now, this file has been removed
and should be replaced later when OdtCursor gains additional tests.
Remove SelectionMover functions that are only used in tests

There are no worthwhile unit tests in SelectionMoverTests after these
are cleaned out, so for now the whole class file has been removed.

Mid-term, the SelectionMover class is to be removed as soon as an
implementation of navigate-by-line-boundaries has been created for
the step-iterator approach.
Merge pull request #389 from peitschie/steps-cleanup

Remove parts of the obsolete SelectionMover interface
Normalize line endings on Windows platform to line-feed

This ensures maximum compatibility with existing tools such as updateJS.
Fix various paths that must be denormalized on Windows in updateJS
Cope with absolute file destinations on Windows

It is assumed that absolute file sources should be copied to the root of
the target directory.

On unix-based systems, an absolute path begins with a '/', which is
interpreted as 'start at root' and does the right thing. On Windows,
these paths contain ':' (e.g., C:/Source) which is an invalid path.
Improve diagnostics output if class definitions are missing
Update current directory magic in runtime.js

Previous behaviour caused build problems on Windows. New logic does the
same thing (effectively) as the previous implementation (i.e., if the
script path is relative, set the current directory of the runtime),
whilst avoiding build failures on Windows.
Handle absolute paths in nativeQTClient's application.qrc
Economise on command line length by passing in CC flags via file

Windows has an upper limit of 8000 chars in a single command, which the
current CC compilation command exceeds. Passing in the flags via file
saves about 900chars and allows this command to run.
Copy node modules locally so NodeJS picks them up

NodeJS makes it difficult to load modules outside the current folder,
and CMake makes it difficult to set environment variables. This is non
ideal, but at least functions correctly.