GitLab

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

After qmljsdebugger was moved to share/, the build order of
qmlobserver and qmljsdebugger had to be re-adjusted.

Reviewed-By: Lasse Holmstedt

see 576642a7 for details

This widget has little to do with the QML debugging library, and will be
reused inside the QML JS Inspector UI as well.

Makes it look ugly

Now the style is something similar to Qt Creator's default coloring.

The problem was that qtLibraryTarget only works for libraries (see
mkspecs/features/qt_functions.prf), not apps. Additionally,
because we now have an app bundle inside an app bundle for OS X, the
install name of the library has to be manually modified.

Reviewed-by: con

QMLObserver links against the library dynamically. User's apps can also
link to it statically, so that the app can be deployed with debugging
features to a device, without having to worry about library deployment.

Fixes issues with reloading freezing on Gnome

They would need special treatment, like the Qml extended objects. The
issue is they lead to two meta objects with the same classname and the
dumper can't handle that.
(cherry picked from commit 206c190e)

(cherry picked from commit 619d50f0)

To show the object string id's, the debug protocol is used to get them.
The problem is that the required methods in QDeclarativeContext(Data)
are not exposed, and it's too late to do it for 4.7.0. Hence this change
should be reverted in 4.8 when more efficient way of getting the id's
comes available.

All the expended item need to be retreived before we can call endCycle

Skip all signals and slot, there is too many of them,
and it is not usefull in the debugger.