We have to check for Qt Versions and private headers to build qmlpuppet.

Reviewed-by: Kai Koehne

The complete qml emulation layer (instances) is moved
into another external process (qmlpuppet).

Summary of architectural changes:

- Asynchronous messaging
    Handling commands and data transfer asynchronously reduces the
    amount of context switches between processes.

- Proxy classes for client process
    This classes abstract the inter process communication

- QVariant based command parsing and serialization
    Using LocalSocket in bidirectional manner for communications
    of commands and data transfer.

- Integer based identifier instead of ModelNode in client process
    The qml emulation layer (instances) has no more depencies to our
    internal data model.

- Timer based rendering
    Rendering in instances is controlled by a timer. Only dirty items
    are updated.

Requested-by: Maurice Kalinowski

This creates a .pro from all "source" files below a given directory.
As I'd like to use Qt Creator as tool to quickly inspect and navigate
"alien" codebases a way to easily set up dummy .pro files is needed.
qmake -project takes far too long on projects of the size of Qt itself.

Reviewed-by: Robert Loehning <robert.loehning@nokia.com>
Task-number: QTCREATORBUG-2827

Discussed-with: kkoehne

Moved qmljsdebugger to a dir under qml/, made qmlobserver compile
without creator dependencies and made it compile with debugging
helpers.

Reviewed-by: hjk

Must be compiled during runtime - otherwise, the app may not work
with Qt that is compiled with another compiler.

Reviewed-by: hjk

qmlInspectorContext() has been renamed into qmlObserverContext()
in commit  a10b2692.

Reviewed-by: Thomas Hartmann

The QApplication object in main() is already destroyed when showWarnings()
is called. Create another instance in this case.

Task-number: QTCREATORBUG-2446
Reviewed-by: Thomas Hartmann

The library not only contains the observer part, but also the javascript
debugger. Reflect this in the namespace.

The class extends the QDDebugService class, _not_ QDDebugServer. It's
right that there is also a QDEngineDebugServer being actually a service
in QtDeclarative, but we should probably fix this one too.

Introduce some more private classes for the coreplugin,
use header include convention
<QtModule/QClass>, de-qobjectify VariableManager.

Don't force users to inherit from QDeclarativeDesignView. Instead we're
using now event filters to let a user attach a QDeclarativeViewObserver
object to a QDeclarativeDesignView.

This should make it easier to debug problems with Qml plugin type
dumping.

Reviewed-by: Roberto Raggi

This is not activated if breakpad and qt-breakpad is not availiable.

- Changed generator to generate:
- Changed AST::lastToken to return 1 if there is none
- Changed Bind.cpp to set the scope of the block following a control
  statement to extend upto (and not including) the first token after
  the block. So basically, including any whitespace after the control
  statement.

Reviewed-by: Roberto Raggi

Reviewed-by:  Lasse Holmstedt

Try to make the observer mode less intrusive by removing the toolbar,
and making the crumblepath only when mode is active / an overlay.

 * Fix all warnings about non-explicit constructors except for those
   in 3rdparty code.

The builtin QML plugins require to be imported with the full uri, i.e.
import Qt.labs.particles 1.0
so setting the import path to imports/Qt/labs and doing
import particles 1.0
is not supposed to work. (see QTBUG-11139)

This change adjusts qmldump to take an import path *and* the import uri,
so it will be able to dump the type information for these plugins.

Reviewed-by: Erik Verbruggen

Reviewed-by: hjk

A new debugger engine, QmlCppEngine, is introduced, which wraps gdb
and qml engines into one. Alternatively, if using Windows, Cdb is used
instead of Gdb.

Most of the debugger ui switcher is now rewritten, and it is tailored
for the QML and CPP layout case, the only one supported anyway.

Reviewed-by: hjk