remove no more needed returning of the class constructor at end of class files

runtime.loadClass(...) no longer expects that eval(fileContent) yields
the constructor, and a few loaded files rely on that (e.g. all singletons/namespaces),
so let's be consistent
Merge pull request #606 from kossebau/removeNowUnneededClassReturning

remove no more needed returning of the class constructor at end of class files
Apply merged paragraph styles using OpSetParagraphStyle

Reduce the complexity within the remove text operation and push it up to
the controller instead.
Merge pull request #599 from peitschie/style-via-setstyle

Apply merged paragraph styles using OpSetParagraphStyle
Ignore test-generated artifact
Remove obsolete length parameter from step insert/remove cache signals

The length parameter is incorrect under many circumstances, and has
proven so difficult to get correct that the cache implementation now
ignores it entirely. Remove this tech debt to simplify future ops.
Eliminate unnecessary conversion from cursor steps to range
Remove unnecessary (and impossible to use) constraint argument

The constraint function only allows a choice between two adjacent steps
if the supplied position is not exactly on a step. With things such as
inline roots and other complex features of the addressing system, this
is extremely difficult to use correctly.

As it is currently unused, the best thing to prevent future problems it
to terminate it now!
Remove unnecessary test returns (again!)

These were just cleaned up, and here someone has gone and reintroduced
them again! What gives!
Merge pull request #600 from peitschie/cleanup

Remove sharp edges from various APIs
WebODF viewer is now part of ViewerJS, so remove outdated README-viewer.odt
Merge pull request #592 from kossebau/removeOutdatedViewerDoc

WebODF viewer is now part of ViewerJS, so remove outdated README-viewer.odt
Move bitrotted programs for iOS, Playbook and Qt to attic/
Merge pull request #583 from kossebau/moveBitrottedAppsToAttic

Move bitrotted programs for iOS, Playbook and Qt to attic/
Simplify CSS rules for cursor and composer element

The cursor node is now completely hidden when not in use, so there is no
need to touch the height or width properties of the composer or cursor.

In addition, the new overlay caret no longer requires the composer to be
displayed as an inline-block in order to function.
Provide a better caret position fallback when no visible rects are found

In the specific situation where there are no visible rectangles nearby
from which to calculate the caret position and size, the cursor node itself
will be made visible with some hidden internal text as a substitute.

This ensures the caret is correctly aligned in empty paragraphs that are
not left-aligned, or in an area surround by non-visible rects such as near
multiple annotations.
Remove another unnecessary inline-block

The cursor element is now only visible when it contains either text
or the caret-size helper. In addition, there are no longer any fixed
widths being applied to the cursor element, so the inline-block is not
necessary.
Merge pull request #611 from peitschie/cursor-visible

Provide a better caret position fallback when no visible rects are found
Only store the start node in DomUtils.getNodesInRange if within range

Fixes a regression introduced in 8b742ee. The currentNode was being
incorrectly added to the results array before it was checked to see if
it was contained inside the supplied range.
Merge pull request #612 from peitschie/range-fixup

Only store the start node in DomUtils.getNodesInRange if within range