Qml debugging is now disabled by default, and has to be enabled
explicitly (b2016bbfc9). This has to be done before the
QDView/QDEngine is instantiated ...
The patch introduces a static create method to QmlApplicationViewer,
so that the setup can be hidden from the users main file.
Qml Debugging requires 4.7.1, and the path of qmljsdebugger being
specified on the command line. Just disable debugging if this
isn't the case instead of bailing out an error.
Reviewed-by: dt
Qml debugging is now disabled by default, and has to be enabled
explicitly (b2016bbfc9). This has to be done before the
QDView/QDEngine is instantiated ...
The patch introduces a static create method to QmlApplicationViewer,
so that the setup can be hidden from the users main file.
Reviewed-by: Alessandro Portale
...and do not call it show(), because that is the signature of
a non-virtual base class function. showExpanded() sucks as name,
and hjk, who reviewed this is not convinced.
But showExpanded() is still better than show().
Task-Number: QTCREATORBUG-2979
Reviewed-By: hjk
- Renaming the screen orientation enum and keys
- Explicit constructors
- Virtual destructors
- Renamed some occurences of 'Qml' in comments to 'QML'
- Adding descriptive comments to all generated files which should
not be touched by the user.
- Adding missing license headers to the qmljsdebugger sources
Task-Number: QTCREATORBUG-2885
Reviewed-by: Friedemann Kleint
Reviewed-by: dt
Don't confuse users by two defines they have to comment in when
they just want to 'debug': Instead QMLJSDEBUGGER now activates
both the Js Debugger & and the QmlObserver services. Finetuning
can still be done by using the (undocumented) NO_JSDEBUGGER,
NO_QMLOBSERVER defines.
This was committed to the master branch, but was supposed
to go into 2.1 (I misunderstood the branching strategy of
Creator 2.1).
Since this does not change Creator code:
Reviewed-by: Trustme
This allows us to enable/disable the experimental observer, independent
from the core javascript-debugger functionality.
Reviewed-by: Christiaan Janssen
Don't force users to inherit from QDeclarativeDesignView. Instead we're
using now event filters to let a user attach a QDeclarativeViewObserver
object to a QDeclarativeDesignView.
- Removed the "cpp/" dir
- Moved main.cpp and symbianicon.svg next to the main .pro.
This also reduces the dir depth in the project view.
- Introduced "qmlapplicationviewer/" dir, which will contain the files
which the user should not modify. All the files there have the base
name "qmlapplicationviewer"
- Moved/renamed "qmlapplication.pri" to
"qmlapplicationviewer/qmlapplicationviewer.pri"
