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.

QVariant does not work as they can contain custom type that corrypt the stream

When the document is reloaded by the server, we need to refresh
refresh what was the loaded document, and refresh the debugIds

Unfortunatelly, streaming QVariant is not a really good idea, as streaming
a custom type would fail