| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Task-number: QTBUG-13799
Reviewed-by: Martin Jones
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The protocol so far was client->server only. That is, there was no
sane way for a client to check whether a plugin on the server (service)
was available or not. E.g. calling Client::setEnabled(true) 'succeeded',
without a check whether there is actually a service to talk to.
The new protocol replaces this shortcoming by a service discovery
mechanism: Both client & service announce their available plugins at
handshake time, and later on if there are changes. The status is
reflected in Client::status() and Service::Status() , which are either
NotConnected - no network connection, or not registered properly
Unavailable - TCP/IP connection works, but no plugin with the same
name on the other side
Enabled - You can connect to plugin on other side
The status changes happen automatically (no setEnabled() anymore).
Furthermore a version ID was added to the handshake, so that we can
extend the protocol further in the future :)
|
|
|
|
|
|
|
|
|
|
| |
The environment variables do not work for Symbian devices, so
without this change, QML debugging cannot be done on them.
In addition, configure now contains an option to disable qml
debugging entirely, due to it being a major security risk.
Reviewed-by: kkoehne
|
|
|
|
|
|
|
| |
Some public context are within the internal context, so we need to stream
them to get every objects
Reviewed-by: Lasse Holmstedt
|
|
|
|
| |
QTBUG-11933
|
|
|
|
|
|
|
| |
The new message currently enables resetting bindings, literal values and
signal handlers (onX: {...}) through the debugger.
Reviewed-by: Roberto Raggi
|
|
|
|
| |
Task-number: QTBUG-10035
|
|
|
|
|
|
| |
the engine until a debug client has connected. This makes for easier
debugging from Qt Creator when debugging C++ and QML together and when
debugging an application that has multiple engines.
|
|
|
|
|
| |
Task-number:
Reviewed-by: Martin Jones
|
| |
|
| |
|
|
|
|
| |
There's nothing meta about our properties.
|
|
|
|
|
|
| |
We don't want to allow manipulation of bindings and signal properties through
the public API. Equivalents of the public functions now exist in
QDeclarativeMetaPropertyPrivate for internal use.
|
| |
|
|
|
|
| |
to QDeclarativeXXX.
|
|
QDeclarativeXXX.
|