If the user aborts state renaming or gives the state the same
name again there is no MessageBox shown anymore.

Using '/' was legacy and is just confusing.
The code is way more consistent now with QmlJS and does not require
conversions.

Qt 4.7 imports are converted to QtQuick 1.0 imports.

The custom notification code leads to hard readable code.

But still slow.

Reviewed-by: hjk

fixes crash on shutdown

Reviewed-By: Thomas Hartmann

The removed node is propably not a state.

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.

We need to support the N900

Reviewed-by: Kai Koehne

huge renaming from Qt to QtQuick
propertyeditor qml files moved from Qt to QtQuick
auotests fixed
files used in tests fixed

autotests pass

Task-number: QTCREATORBUG-2556

Reviewed-by: Kai Koehne

Task-number: QTCREATORBUG-2507

There might be files without an import for Qt
States require "Qt"
I also added try {} catch blocks to the state editor,
to avoid issues like this.

Reviewed-by: Kai Koehne

Before this patch the thumbnail drawing  triggered global
state changes.

Reviewed-by: Marco Bubke

Bauhaus now uses only one single instance view.

Done by Marco Bubke

nodeInstancePropertyChanged() is called for _every_ state switch ... so
the current assumption that it only reflects real changes does not hold.

Instead, use the orphaned sceneChanged() method to schedule redraws.
However, this still results in some overhead when switching to the base state
(sceneChanged() cannot decide whether it has to redraw all other states
or not).

Reviewed-by: Christiaan Janssen

QmlDesigner.StatesEditor:  speed up by only updating thumbnails after rewritter transactions are finished

This is needed to suppert inline script function of Qml in the designer

Of course disabled by default

forwarding to QmlModelView::customNotification(); was missing

it missing since ever but the code I removed in
861981a3 shadowed this.

Reviewed-by: Kai Koehne

Before recent refactoring (done by Marco) the node instances were not
able to handle outside the current state. So we had to change back to
the base state for all base state changes from the rewriter.

This is not necessary, anymore.

Reviewed-by: Marco Bubke

The states editor horizontal scrollbar was broken because the
setCurrentStateSilent() call was causing a loop, calling
nodeInstancePropertyChanged() when state property is changed. Because
rendering of states changes the "state" property, the calls never
stopped. Now StatesEditorView has a flag which prevents the loop.

Reviewed-by: Christiaan Janssen

Reviewed-by: kkoehne

Reviewed-by: Marco Bubke

Reviewed-by: Thomas Hartmann

Schedule a redraw of the states icons when an element is removed from
the model.

Task-number: BAUHAUS-460
Reviewed-by: Christiaan Janssen