Also apply changes to the .qml file in e.g. the Design mode to
the running application.

This is convenient especially in the observer mode.

Reviewed-by: Christiaan Janssen

If the user clicks on an instance of an element in the running app
while in server mode, the cursor selection is automatically updated.
However, the change of the cursor then leads to all the other
instances of the element at the cursor position being selected too.

Prevent this 'call back' in the QmlInspector by checking whether one
of the newly selected items is the one just selected.

Simpler mechanisms (like a sequential blocking of updates) don't
work because the call back happens through a QTimer.

Task-number: QTCREATORBUG-2366

Rename setSelectedItemsByObjectReference slot to gotoObjectDefinition

Give m_client, m_designClient member variables more descriptive names.

Simplify method names.

Change signature of setSelectedItemsByObjectId to match the one from
signal currentObjectsChanged.

There's  some 'external' and some 'internal' part now. Other plugins
are only supposed the external interface.

Qml Applications by default copy the qml files into XX.app/Contents/Resources in
the shadow build directory. Take this into account when trying to find the files in the source directory.

Reviewed-by: Alessandro Portale

... instead of running a sed script over a lot of files on each
version increment.

Krazy complained about missing Q_OBJECT macros. Fix them.

Clean icore.h.

Move internal classes QmlJSEditorEditable/SemanticHighlighter
out of qmljseditor.h. Move QmlJSEditor from namespace
QmlJSEditor::Internal to QmlJSEditor.

Reviewed-by: Christian Kamm <christian.d.kamm@nokia.com>

Check that the node under cursor is indeed a UiObjectMember

Reviewed-by: Christiaan Janssen
Task-number: QTCREATORBUG-2760

At the time setupToolbar is called in the shutdown process the
connection still exists. Instead just use the parameter.

Task-number: QTCREATORBUG-2693
Reviewed-by: Christiaan Janssen

It only works together with qmlobserver. Making it disabled for .pro
file based projects would require some infrastructure.

Reviewed-by: Christiaan Janssen

Separate QmlObserver button + submodes from the general Preview &
Reload functionality.

Task-number: QTCREATORBUG-2163
Reviewed-by: Christiaan Janssen

Make sure that the 'artifical' URL of the item created actually is
absolute (starts with a file:///). Otherwise an Assert will be hit
when the imports include e.g. a .js file, and the Engine tries to
load it.

Task-number: QTCREATORBUG-2644
Reviewed-by: Olivier Goffart

Don't try to disconnect from the proxy if you haven't been connected
before, e.g. because the QmlJSObserverService is missing.

Reviewed-by: Christiaan Janssen

We disabled it because it should be considered experimental ...
but this creates problems with the debugger setup (Observer pane
doesn't show up even if the plugin is activated).

Carsten Owerfeldt agreed with this.

ClientProxy::isEnabled() now only returns true when the server plugins
are available too. Wait until then before using it to initialize
the livepreview objects.

Reviewed-by: Lasse Holmstedt

We've to wait with reloadEngines until the services are actually
enabled.

Reviewed-by: Christiaan Janssen

Reviewed-by: Christiaan Janssen

Protocol / classes changed with commit fd9771c29d

Reviewed-by: Christiaan Janssen

Should have been done earlier. 2.1.80 was burned in the pre-2.1.0->2.0.1
days, and we'd like to have odd subminor for 'working' and even subminor
numbers for pure cherry-picking release branches anyway.

Reviewed by:  Thomas Hartmann