1. 10 Jan, 2011 1 commit
  2. 17 Dec, 2010 1 commit
  3. 10 Dec, 2010 2 commits
  4. 08 Nov, 2010 2 commits
  5. 05 Nov, 2010 1 commit
  6. 02 Nov, 2010 1 commit
  7. 10 Sep, 2010 1 commit
    • Friedemann Kleint's avatar
      I10N: First translation fixes for 2.1 · 24cadd34
      Friedemann Kleint authored
      Fix README, some spelling errors, remove contractions,
      exclamation marks, correct some plural forms, join split messages.
      Add QCoreApplication::translate to non-Q_OBJECT-classes.
      Fix some lupdate warnings about discarding meta-data (//:).
      24cadd34
  8. 07 Sep, 2010 1 commit
  9. 18 Aug, 2010 1 commit
  10. 30 Jul, 2010 1 commit
    • Alessandro Portale's avatar
      Pedantic cleanup of filename parameters for QIcon constructor · 3aa3c568
      Alessandro Portale authored
      Using more *::Constants::ICON_* where it makes sense and
      wrapping the file names into QLatin1String where they were
      missing.
      
      The increased usage of the ICON constants needed a few more
      cross plugin includes of *constants.h, here and there.
      I think that it is OK, since the dependencies were alredy there
      icon resource wise.
      3aa3c568
  11. 22 Jul, 2010 1 commit
  12. 21 Jul, 2010 1 commit
  13. 20 Jul, 2010 1 commit
  14. 15 Jul, 2010 1 commit
  15. 14 Jul, 2010 2 commits
  16. 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
  17. 15 Jun, 2010 1 commit
  18. 22 Mar, 2010 1 commit
  19. 18 Mar, 2010 1 commit
  20. 05 Mar, 2010 2 commits
  21. 03 Feb, 2010 1 commit