When a change is done to an element that cannot be changed due to
debugger/qdeclarative limitations, a warning is shown to the user in QML
JS Editor.

Reviewed-by: Olivier Goffart

Reviewed-by: Thomas Hartmann

Reviewed-by: Tobias Hunger

Reviewed-by: Roberto Raggi

Block selection was "broken" when using tabs, or rather
incomplete: It treated tabs as normal characters, which
has shown to be unexpected by people using tabs in code.

The new implementation has a vastly improved find scope
as well. In addition, creating a blog selection with
mouse or keyboard feels a lot more solid now, as the
actual selection is detached from possible valid cursor
positions.

Task-number: QTCREATORBUG-1541

Reviewed-by: kh1

Apparently creator uses the kate highlighter file to find the
mumetype of a file.
But kate annotate qml file with text/x-qml instead of application/x-qml
that we expect

see 576642a7 for details

This one should be called when a component is changed and components
using it need to be reloaded.

To catch cases of invalid code like this:
struct A : B {};
struct B : A {};

Reviewed-by: Roberto Raggi

Reviewed-by: kh1

Do not use scaled on null pixmaps

* Proper implementation using a timer

* We also do a revision check now

* The RefactorMarker is only shown for types that we support

isAvailable() returns true if a Quick ToolBar is available
for that node

Details: No mocables in source file, no need for #include then.

Qml Debugger: When we pause, notify creator that we paused, so it does not get in an inconsistant state

Reviewed-by: kh1

Task-number: QTCREATORBUG-1886