aboutsummaryrefslogtreecommitdiffstats
path: root/qbs/imports/QtcDocumentation.qbs
diff options
context:
space:
mode:
authorhjk <hjk@theqtcompany.com>2016-06-03 19:11:29 +0200
committerhjk <hjk@theqtcompany.com>2016-06-08 08:16:22 +0000
commitdb9437c2e83ec11befa855e4806ac7920d1a5800 (patch)
tree08eaaef00d991b8271513631709bc0475661e311 /qbs/imports/QtcDocumentation.qbs
parent1e909269663ac02bd9b50a1eca5e7df62eb144f5 (diff)
Generalize IDevice::qmlProfilerHost
The idea is to have a way for tools to specify what kind of control channel they would like to use to communicate with a device without making the choice explicit dependent on the exact kind of tool to further decouple device and tool implementations. The 'hint' values are there to help the device implementation to decide on which channel to use exactly in case there are multiple choices. In any case, the tool is responsible to check that the returned channel is suitable for its operation. Currently the only choice is "QmlControlChannel" yielding a simple wrapper around the former IDevice::qmlProfilerHost() return value. Other enum values may potentially be {Tcp,LocalSocket}ControlChannel (to specify a type of transport) AdbChannel (to specify some generic helper mechanism). It might also turn out that something more complex than an enum will be needed, e.g. to express a set of values with priorities or such, but I'd rather avoid overengineering for now. Change-Id: Id386425eb3dd2bb395065f0bdb6f67217cd40a71 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Diffstat (limited to 'qbs/imports/QtcDocumentation.qbs')
0 files changed, 0 insertions, 0 deletions