1. 04 Jul, 2016 1 commit
  2. 22 Jun, 2016 1 commit
  3. 14 Jun, 2016 1 commit
  4. 13 Jun, 2016 3 commits
  5. 10 Jun, 2016 5 commits
  6. 08 Jun, 2016 1 commit
    • hjk's avatar
      Generalize IDevice::qmlProfilerHost · db9437c2
      hjk authored
      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's avatarUlf Hermann <ulf.hermann@qt.io>
      db9437c2
  7. 03 Jun, 2016 1 commit
  8. 31 May, 2016 1 commit
  9. 26 May, 2016 1 commit
  10. 20 May, 2016 2 commits
  11. 19 May, 2016 1 commit
  12. 13 May, 2016 1 commit
  13. 11 May, 2016 1 commit
  14. 09 May, 2016 2 commits
  15. 02 May, 2016 2 commits
  16. 29 Apr, 2016 3 commits
  17. 25 Apr, 2016 1 commit
  18. 21 Apr, 2016 1 commit
  19. 20 Apr, 2016 3 commits
  20. 19 Apr, 2016 2 commits
  21. 15 Apr, 2016 1 commit
  22. 10 Apr, 2016 1 commit
  23. 30 Mar, 2016 2 commits
  24. 14 Mar, 2016 1 commit
  25. 10 Mar, 2016 1 commit