1. 23 Feb, 2017 1 commit
  2. 26 Jan, 2017 1 commit
  3. 22 Nov, 2016 1 commit
  4. 16 Nov, 2016 1 commit
  5. 01 Nov, 2016 1 commit
  6. 05 Oct, 2016 1 commit
  7. 29 Sep, 2016 1 commit
  8. 26 Aug, 2016 1 commit
  9. 23 Aug, 2016 1 commit
  10. 05 Aug, 2016 1 commit
  11. 04 Aug, 2016 1 commit
  12. 02 Aug, 2016 1 commit
  13. 21 Jul, 2016 1 commit
  14. 18 Jul, 2016 1 commit
  15. 14 Jul, 2016 2 commits
  16. 28 Jun, 2016 2 commits
  17. 22 Jun, 2016 1 commit
  18. 14 Jun, 2016 1 commit
  19. 09 Jun, 2016 1 commit
    • hjk's avatar
      Debugger: Remove debuggerstringutils.h · 726b907c
      hjk authored
      With QT_RESTRICTED_CAST_FROM_ASCII making GdbMi etc operate on
      QString is feasible again. Take this as opportunity to move
      debugger encoding handling closer to a 'conversion on input and
      output if needed, storage in QString only' scheme.
      
      Change-Id: I2f10c9fa8a6c62c44f4e6682efe3769e9fba30f7
      Reviewed-by: Christian Stenger's avatarChristian Stenger <christian.stenger@qt.io>
      726b907c
  20. 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
  21. 01 Jun, 2016 1 commit
  22. 30 May, 2016 1 commit
  23. 20 May, 2016 1 commit
    • hjk's avatar
      ProjectExplorer: Move Runnable/Connection model into class · 4320aeea
      hjk authored
      Somewhat better encapsulation.
      
      Removes the "false" sharing of Concept implementations, and takes
      the opportunity to change the operator==() into a 'canReUseOutputPane'
      function to be explicit about its only use.
      
      This doesn't solve the change in output pane reuse behavior yet,
      but provides the base to put the required logic into canReUseOutputPane,
      as opposed to abusing the general equality concept.
      
      Change-Id: Id9e4e6b8601c5fcf40a252fb423c2c4c2b74ddb6
      Reviewed-by: Christian Stenger's avatarChristian Stenger <christian.stenger@qt.io>
      4320aeea
  24. 18 May, 2016 1 commit
  25. 17 May, 2016 1 commit
  26. 13 May, 2016 1 commit
  27. 12 May, 2016 2 commits
  28. 09 May, 2016 1 commit
  29. 04 May, 2016 1 commit
  30. 03 May, 2016 1 commit
  31. 29 Apr, 2016 1 commit
  32. 26 Apr, 2016 1 commit
  33. 22 Apr, 2016 1 commit
  34. 21 Apr, 2016 3 commits
  35. 20 Apr, 2016 1 commit