(In QtCreator the wizard would take care of that.)

To keep the breakpoint state machinery simple

Task-number: QTCREATORBUG-3084

Task-number: QTCREATORBUG-2924
Reviewed-by: ck

Task-number: QTCREATORBUG-3090
Reviewed-by: ck

A full evaluate() call resolves the property and continues to the
underlying type. If we use Evaluate::reference() instead, we only the
first step is done and we can get at the source location if a
ASTPropertyReference is returned.

Reviewed-by: Erik Verbruggen

Task-number: QTCREATORBUG-2607
Reviewed-by: Erik Verbruggen

Reviewed-by: Erik Verbruggen

Reviewed-by: con

Reviewed-by: hjk
Task-number: QTCREATORBUG-3099

Task-number: QTBUG-15170

Clear controls that are not applicable to type, but save
and restore their value once the type is again choosen.

Remove BreakHandler::hasPendingBreakpoints, handle new types
in CDB and gdb. Start fixing Breakpoint-Dialog.
Add assignment of Breakpointresponse from BreakpointParameters.

Reviewed-by: hjk

First usage: convert QML examples into c++ projects.

Conflicts:
    share/qtcreator/static.pro
    src/plugins/qmljseditor/qmljsoutlinetreeview.cpp
    src/plugins/projectexplorer/outputwindow.cpp