1. 28 Jul, 2017 1 commit
  2. 20 Jul, 2017 3 commits
  3. 18 Jul, 2017 2 commits
  4. 17 Jul, 2017 4 commits
  5. 14 Jul, 2017 1 commit
  6. 12 Jul, 2017 2 commits
  7. 11 Jul, 2017 1 commit
  8. 10 Jul, 2017 2 commits
  9. 07 Jul, 2017 3 commits
    • hjk's avatar
      ProjectExplorer: Remove RunControl::worker<Type>() · 8376afd9
      hjk authored
      It looks like the case where workers need talk to each other by
      only knowing the type of the 'partner' does not exist in practice
      anymore. With the now-common setup of a 'primary' worker that one
      can introduce the 'lesser' workers to each other directly.
      
      That's also conceptually more robust that picking a partner by
      type only only from some 'pool' (all the workers in a runcontrol),
      scales better (it e.g. is imaginable that a RunControl needs
      more than one PortGatherer in complex setups where more than one
      device is involved) saves a few cycles, and even removes the need
      for workers to be qobject_cast-able.
      
      Change-Id: Ib3d8c942c893d6c198d9813cce7df28ba3260ce8
      Reviewed-by: Christian Kandeler's avatarChristian Kandeler <christian.kandeler@qt.io>
      Reviewed-by: default avatarhjk <hjk@qt.io>
      8376afd9
    • Orgad Shaneh's avatar
      RunConfig: Do not log debug messages to output pane · 2dc90696
      Orgad Shaneh authored
      Looks like this was done for debugging, but the user is not supposed to be
      aware of internal implementation.
      
      Change-Id: If24a2b0f85a04c2e88c5ef5fd66d34a606d46712
      Reviewed-by: Orgad Shaneh's avatarOrgad Shaneh <orgads@gmail.com>
      2dc90696
    • hjk's avatar
      ProjectExplorer: Remove Connection as concept · f82bb1ec
      hjk authored
      It turns out that one "Connection" per RunControl doesn't map
      well to the uses we have. Instead, RunWorkers need to know
      individually how to connect to the place where they can work,
      but they are already specific enough to be able to use a
      standard class (like QUrl) as their way to specify the needed
      entry point.
      
      In theory one could see a RunControl's connection as an
      aggregation of its workers connection bits, but that does
      not really seem to be needed in code.
      
      As consequence, replace UrlConnection by a plain QUrl, and also
      the HostName connection by a QUrl with hostName set.
      
      Change-Id: I40c97e37779314ac0a77041e864a18eadb78f987
      Reviewed-by: Vikas Pachdha's avatarVikas Pachdha <vikas.pachdha@qt.io>
      f82bb1ec
  10. 05 Jul, 2017 1 commit
    • hjk's avatar
      ProjectExplorer: Fix recent indeterministic state of stop button · d857fa52
      hjk authored
      The recent RunControl related changes have led to several regressions
      in the fragile handling of button states in the output pane.
      
      Take advantage of the new Starting phase to fix disabling of the
      run and enabling of the stop button at reasonable times.
      
      Change-Id: Iae191a840484dd08d61facf6b9f439bfafcbbcb0
      Task-number: QTCREATORBUG-18508
      Reviewed-by: Tobias Hunger's avatarTobias Hunger <tobias.hunger@qt.io>
      d857fa52
  11. 04 Jul, 2017 1 commit
  12. 03 Jul, 2017 1 commit
  13. 30 Jun, 2017 1 commit
  14. 29 Jun, 2017 1 commit
  15. 28 Jun, 2017 1 commit
  16. 27 Jun, 2017 1 commit
  17. 20 Jun, 2017 1 commit
  18. 15 Jun, 2017 1 commit
  19. 13 Jun, 2017 1 commit
  20. 29 May, 2017 1 commit
  21. 15 May, 2017 1 commit
  22. 09 May, 2017 1 commit
  23. 08 May, 2017 1 commit
  24. 05 May, 2017 1 commit
  25. 04 May, 2017 2 commits
  26. 03 May, 2017 1 commit
  27. 02 May, 2017 3 commits