1. 15 Sep, 2014 1 commit
  2. 12 Sep, 2014 1 commit
  3. 09 Sep, 2014 1 commit
  4. 26 Aug, 2014 1 commit
  5. 25 Aug, 2014 1 commit
  6. 22 Aug, 2014 1 commit
  7. 20 Aug, 2014 1 commit
  8. 07 Aug, 2014 1 commit
  9. 01 Aug, 2014 1 commit
  10. 28 Jul, 2014 1 commit
  11. 24 Jul, 2014 3 commits
  12. 22 Jul, 2014 2 commits
  13. 21 Jul, 2014 1 commit
  14. 17 Jul, 2014 2 commits
  15. 16 Jul, 2014 1 commit
    • Christian Kandeler's avatar
      QbsProjectManager: Reparse project before building. · e6394559
      Christian Kandeler authored
      
      
      Otherwise, if "save before build" is enabled and the user presses Ctrl+B
      with unsaved changes to a project file, these would get ignored due to
      the delay (and also if the delay were not there, because the file system
      watchers trigger later than the "Build" action).
      If there are no actual changes to any build file, the overhead caused by
      this operation consists of loading (and possibly storing) the build
      graph file.
      
      Task-number: QBS-596
      Change-Id: I1f837cc0fcdc77a249b423834f4b6711f5c0bc87
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@digia.com>
      e6394559
  16. 14 Jul, 2014 1 commit
  17. 11 Jul, 2014 2 commits
    • Christian Kandeler's avatar
      QbsProjectManager: Do not reparse the project after every build. · 473692aa
      Christian Kandeler authored
      
      
      While it is true that additional information about target
      artifacts can appear during a build, this data is already
      present in the qbs::Project object and can simply be retrieved.
      No reparsing is necessary.
      The exception is when reparsing was requested while the build
      was going on. In that case, we really need to do it after
      the build has finished.
      
      Change-Id: Ief3797782ad0ca5651974d4b5d3d64e1199ca9a5
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@digia.com>
      473692aa
    • Christian Kandeler's avatar
      QbsProjectManager: Sanitize QbsProjectNode. · 853497fb
      Christian Kandeler authored
      
      
      The current code keeps an instance of QbsProject and of qbs::Project in
      every project node, with them being null/invalid everywhere except for
      the top-level node. Instead, introduce a dedicated class for the root
      node and hold a QbsProject only there. The qbs::Project is held in
      QbsProject now.
      As a nice side effect, this also fixes QBS-644, presumably because the
      dubious-looking use of projectNode() has been removed.
      
      Task-number: QBS-644
      Change-Id: I5d36806745b9d67879db6f48aa56bc97868e4f17
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@digia.com>
      853497fb
  18. 04 Jul, 2014 1 commit
  19. 24 Jun, 2014 1 commit
  20. 20 Jun, 2014 1 commit
  21. 17 Jun, 2014 1 commit
  22. 06 May, 2014 1 commit
  23. 02 May, 2014 2 commits
  24. 28 Apr, 2014 1 commit
  25. 28 Mar, 2014 1 commit
  26. 27 Mar, 2014 1 commit
  27. 03 Mar, 2014 1 commit
  28. 28 Feb, 2014 2 commits
  29. 27 Feb, 2014 1 commit
  30. 19 Feb, 2014 1 commit
    • Fawzi Mohamed's avatar
      qml: moving most of ModelManager logic to ModelManageInterface · d24cb60d
      Fawzi Mohamed authored
      
      
      Currently ModelManager contains lot logic, but as it sits in QmlJSTools
      it is not possible to use it in standalone tests.
      Moving most of the logic to ModelManagerInterface (and cleanup)
      to allow better testing, and refactoring.
      This introduces a dependency of the qmljs lib on the cplusplus lib
      Also a (small) part of the CppTool::ModelManagerInterface has been
      moved to CPlusPlus::CppModelManagerBase to remove the dependency on
      CppTools to gather the Qml types exposed from C++.
      
      Change-Id: Icad7fe96dfd0f1a2b1058d82bd98c77c40aa5e9d
      Reviewed-by: default avatarFawzi Mohamed <fawzi.mohamed@digia.com>
      d24cb60d
  31. 21 Jan, 2014 1 commit
  32. 14 Jan, 2014 1 commit
  33. 08 Jan, 2014 1 commit