1. 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
  2. 03 Jun, 2016 1 commit
  3. 31 May, 2016 1 commit
  4. 26 May, 2016 1 commit
  5. 20 May, 2016 2 commits
  6. 19 May, 2016 1 commit
  7. 13 May, 2016 1 commit
  8. 11 May, 2016 1 commit
  9. 09 May, 2016 2 commits
  10. 02 May, 2016 2 commits
  11. 29 Apr, 2016 3 commits
  12. 25 Apr, 2016 1 commit
  13. 21 Apr, 2016 1 commit
  14. 20 Apr, 2016 3 commits
  15. 19 Apr, 2016 2 commits
  16. 15 Apr, 2016 1 commit
  17. 10 Apr, 2016 1 commit
  18. 30 Mar, 2016 2 commits
  19. 14 Mar, 2016 1 commit
  20. 10 Mar, 2016 1 commit
  21. 08 Mar, 2016 1 commit
  22. 07 Mar, 2016 1 commit
    • hjk's avatar
      Debugger: Merge debug mode and analyze mode · 92e301a0
      hjk authored
      On the user-visible side, only the 'Analyze' mode button disappears,
      and instead a combobox to switch between different tools in appears
      in the Debug mode toolbar.
      
      Internally, that's quite some re-organzition: The centralized
      'Analyze mode is busy' flag is gone, allowing us to run e.g.
      ClangStaticAnalyzer and MemCheck in parallel.
      
      Analyzer tools and debugger now share the same mechanism to
      generate/load/save dock widgets.
      
      Analyzer tools now create and handle their own start/stop button
      when appropriate. In general, Analyzer tools can create/handle more
      than one run control at a time.
      
      Further consolidation is possible, e.g. RunControl state handling
      could be merged into the base ProjectExplorer::RunControl to
      avoid the still existing duplication in ~15 instances.
      
      Change-Id: I91e5940ebc4211f98056d507cf2f7b5f8efe7f07
      Reviewed-by: default avatarChristian Stenger <christian.stenger@theqtcompany.com>
      92e301a0
  23. 29 Feb, 2016 1 commit
  24. 25 Feb, 2016 1 commit
    • hjk's avatar
      Move analyzerbase to debugger · aaf05f5a
      hjk authored
      This is the first mechanical step to execute on the 'shared pool of
      debugger/analyzer views' idea.
      
      Future steps would be providing infrastructure for the view pool,
      making all analyzer/debugger views use the pool and then re-extract
      a sensible base for a 'analyzer-and/or-debugger' tool plugin interface.
      
      Change-Id: I1bb392e6dd3084fc56937956bee1d6fd9530335d
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>
      aaf05f5a
  25. 24 Feb, 2016 1 commit
  26. 12 Feb, 2016 1 commit
  27. 05 Feb, 2016 1 commit
  28. 04 Feb, 2016 1 commit
  29. 02 Feb, 2016 1 commit
  30. 29 Jan, 2016 2 commits