Done-with: Erik Verbruggen

By always setting the scope object, even if it is identical to the root
object.

Done-with: Erik Verbruggen

Done-with: Erik Verbruggen

Just the declaring member isn't enough.

Instead of only maintaining a flat list of scopes, actually store the
global, component chain, root object, scope object, function, id and js
scopes separately.

Done-with: Christian Kamm

And made the warnings/errors translatable.

Used, for instance, in Rotation.axis or Rotation.origin.

This now errors for:
anchors.undefinedAnchor: foo
x.undefinedAnchor

The idea is that it may be a plugin-provided type. We don't want user
code to be riddled with error markers in that case.

Reviewed-by: Roberto Raggi

Reviewed-by: Roberto Raggi

* Add SemanticHighlighter to QmlJSTextEditor to update the semantic info
  in a background thread.
* Add QmlJS::Check to run semantic checks on qml and js documents.
* Add a check for incorrect property names.
* Fix hoverhandler to show tool tips from extra selections over help
  tooltips.

It is used to evaluate expressions to values.
Done to make room for a real 'check' pass.

* For JS files: Add each Qml component that sources the file in a Script
  tag to the scope chain.
* For Qml components: Add each component that instantiates the component
  to the scope chain.
* Generate the full list of documents required for completion in a
  given file. Previously, files that included the file were missing.