1. 27 Jun, 2017 1 commit
  2. 16 Jun, 2017 2 commits
  3. 12 Jun, 2017 1 commit
  4. 30 May, 2017 1 commit
  5. 15 May, 2017 1 commit
  6. 05 Apr, 2017 1 commit
    • hjk's avatar
      ProjectExplorer: Merge AnalyzerRunControl into RunControl · 112e3222
      hjk authored
      The change is "conceptually wrong", the AnalyzerRunControl derived
      classes' functionality should be provided by ToolRunners based classes
      encapsulating/"being" the current Analyzer*Runner classes.
      
      However, the AnalyzerRunControl is only three (empty even) virtual
      functions, but a big obstacle in merging attempt due to a lot of
      mechanical followup changes in downstream users.
      
      The current construction mechanism of analyzer run controls is actually
      two different mechanisms (locally direct RunControlFactories, and a
      "generic" createAnalyzerRunControl wrapper for remote cases). The generic
      createAnalyzerRunControl makes it difficult to migrated them one-by-one,
      due to the various downstream users.
      
      So instead of merging the per-analyzer two uses directly reduce
      the "indirection" distance by removing the AnalyzerRunControl
      intermediate layer. After that the createAnalyzerRunControl mechanism
      can be dissolved by using normal RunControlFactories also for
      the remote cases. After that, porting to ToolRunner, and combining
      with ther local equivalent can be done one by one.
      
      Change-Id: I0ddace33fcce210cf3a547ac5bb23b3d85013934
      Reviewed-by: Ulf Hermann's avatarUlf Hermann <ulf.hermann@qt.io>
      Reviewed-by: Tobias Hunger's avatarTobias Hunger <tobias.hunger@qt.io>
      112e3222
  7. 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
  8. 29 Feb, 2016 1 commit
  9. 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
  10. 10 Feb, 2016 1 commit
  11. 02 Feb, 2016 1 commit
  12. 29 Jan, 2016 1 commit
  13. 28 Jan, 2016 2 commits
  14. 27 Jan, 2016 2 commits
  15. 26 Jan, 2016 1 commit
  16. 21 Jan, 2016 1 commit
  17. 20 Jan, 2016 1 commit
  18. 19 Jan, 2016 1 commit
  19. 07 Jan, 2016 1 commit
    • hjk's avatar
      Analyzer: Slim down AnalyzerStartParameters · 8150209f
      hjk authored
      * SysRoot can always be determined from kit.
      * Pass around RunMode as extra parameter
        not as part of AnalyzerStartParameters.
        That's closer to the pattern used elsewhere.
      * Environment was always initialized from the runconfig's
        EnvironmentAspect. The tools can do that directly.
      * Provide setter for display name for cases where
        it is not equal to RunConfiguration::displayName
      
      Change-Id: I811a0d7cdeb55cc37a16a593b3942abb567a2150
      Reviewed-by: default avatarBogDan Vatra <bogdan@kdab.com>
      Reviewed-by: default avatarUlf Hermann <ulf.hermann@theqtcompany.com>
      8150209f
  20. 19 Nov, 2015 1 commit
  21. 31 Aug, 2015 1 commit
  22. 08 Jul, 2015 1 commit
  23. 30 Jun, 2015 1 commit
  24. 18 Jun, 2015 1 commit
  25. 17 Jun, 2015 1 commit
  26. 15 Jun, 2015 1 commit
  27. 16 Jan, 2015 1 commit
  28. 09 Oct, 2014 1 commit
  29. 08 Jan, 2014 1 commit
  30. 15 Oct, 2013 2 commits
  31. 16 Aug, 2013 1 commit
  32. 05 Aug, 2013 4 commits
  33. 01 Aug, 2013 1 commit