* property -> lookupMember
* setProperty -> setMember
* removeProperty -> removeMember

Change-Id: I638479ee2b90b684283e714630bdcab237f6b3f2
Done-with: Fawzi Mohamed
Reviewed-on: http://codereview.qt.nokia.com/77


Reviewed-by: Fawzi Mohamed <fawzi.mohamed@nokia.com>

To avoid lots of follow-up errors where the root cause is a failed
prototype resolution or a prototype cycle.

Task-number: QTCREATORBUG-4952
Change-Id: Id474c8c6c152c993aca8c6c421b6d88eb1481676
Reviewed-on: http://codereview.qt.nokia.com/36


Reviewed-by: Thomas Hartmann <Thomas.Hartmann@nokia.com>

Task-number: QTCREATORBUG-4814

UiPublicMember is now initialized with a statement.

Change-Id: I8b73d583be1ee7183f4074bce49d5390e38631a2

To avoid order-of-initialization problems.

Reviewed-by: Thomas Hartmann

Task-number: QTCREATORBUG-2306

(cherry picked from commit a03de5f7)

Fixes the problem 5426c3ac and
7b25f438 worked around.

Reviewed-by: Erik Verbruggen

Don't underline the import if a qmldump fails,
but the typeinfo is available via a .qmltypes file. That should allow
users to 'fix' qmldump issues by shipping a .qmltypes file.

Reviewed-by: Erik Verbruggen

Reviewed-by: Erik Verbruggen

The problem was that several lookup calls suddenly failed because
the actual QML types were no longer in the default scope chain. However,
the QML documentation says the type names are in the scope.

Also, 'MyComponent.' in a JS-expression context only showed the attached
properties of MyComponent and missed the enums.

With this change completion now may offers too many options, but that's
better than missing some.

This reverts parts of 490f2797

Reviewed-by: Leandro Melo

Having a duplicate prototype chain - once in FakeMetaObjects and once
in QmlObjectValues was unnecessary. Now FMOs don't contain references
which may allow other simplifications.

That means createComponent etc. will now be completed.

In preparation of relocatable plugin types.

Task-number: QTCREATORBUG-3048

Reviewed-by: hjk

There was trouble when a plugin qmlRegisterType'd something like 'Item'
into the global default module.

Reviewed-by: Roberto Raggi

By moving the offending code into a background thread.

Reviewed-by: Erik Verbruggen

Previously they were leaked when a qmldump or the C++ exported QML
type list updated.

Just deleting the previous FakeMetaObjects is not an option, as they
might still be used in a QmlObjectValue owned by an Engine.

Reviewed-by: Erik Verbruggen

Reviewed-by: Erik Verbruggen

Those are needed for the Visual Editor

Reviewed-by: Christian Kamm

We should differentiate between int and real

Reviewed-by:  Christian Kamm

* Bind::usesQmlPrototype is now significantly more performant
* type environments are no longer hashed by filename, but rather
  by Document *
* duplicate scope builds are avoided

Task-number: QTCREATORBUG-2835
Reviewed-by: Erik Verbruggen

Reviewed-by: Erik Verbruggen

This will allow distinguishing mere strings from urls and allow
different completion.

Reviewed-by: Erik Verbruggen

We have to follow the prototype chain

Reviewed-by: Christian Kamm