1. 13 Aug, 2010 1 commit
  2. 12 Aug, 2010 1 commit
  3. 23 Jul, 2010 1 commit
  4. 21 Jul, 2010 1 commit
  5. 20 Jul, 2010 1 commit
  6. 15 Jul, 2010 1 commit
  7. 14 Jul, 2010 4 commits
  8. 12 Jul, 2010 1 commit
  9. 09 Jul, 2010 1 commit
  10. 06 Jul, 2010 4 commits
  11. 05 Jul, 2010 1 commit
  12. 02 Jul, 2010 1 commit
  13. 01 Jul, 2010 2 commits
  14. 29 Jun, 2010 3 commits
  15. 28 Jun, 2010 3 commits
  16. 25 Jun, 2010 2 commits
  17. 23 Jun, 2010 1 commit
  18. 22 Jun, 2010 1 commit
    • hjk's avatar
      debugger: The DebuggerEngine refactoring. · 6a6cba55
      hjk authored
      This replaces the (de facto) singleton engines and data handlers by classes
      that are instantiated per run. The DebuggerRunControl will now create an
      object of (a class derived from) DebuggerEngine that contains all the relevant
      "dynamic" data.
      
      DebuggerManager is no more. The "singleton" bits are merged into DebuggerPlugin,
      whereas the data bits went to DebuggerEngine.
      
      There is no formal notion of a "current" DebuggerEngine. However, as there's
      only one DebuggerEngine at a time that has its data models connected to the
      view, there's still some "de facto" notion of a "current" engine. Calling
      SomeModel::setData(int role, QVariant data) with custom role is used as the
      primary dispatch mechanism from the views to the "current" data models
      (and the engine, as all data models know their engine).
      6a6cba55
  19. 14 Jun, 2010 1 commit
  20. 11 Jun, 2010 1 commit
  21. 10 Jun, 2010 5 commits
  22. 01 Jun, 2010 1 commit
  23. 26 May, 2010 2 commits