1. 13 Jul, 2017 1 commit
  2. 12 Jun, 2017 1 commit
  3. 24 Feb, 2017 1 commit
  4. 21 Feb, 2017 1 commit
    • Ulf Hermann's avatar
      QmlProfiler: Add text marks for QML/JS types into documents · 548a86f5
      Ulf Hermann authored
      The text marks are little labels next to the lines in the editor
      that tell you how much of total run time was spent in the
      respective QML/JS construct during the last profiling session.
      This is similar to what the valgrind profiler does.
      
      We add the text marks only when the documents are loaded into an
      editor. This keeps the number of text marks manageable. Multiple
      events on a single line are shown using a tooltip.
      
      Task-number: QTCREATORBUG-17757
      Change-Id: Ie38b8ab880a718a1ef72ef343d84070ab34bc5bc
      Reviewed-by: default avatarhjk <hjk@qt.io>
      548a86f5
  5. 08 Aug, 2016 1 commit
  6. 20 Jul, 2016 2 commits
  7. 18 Jul, 2016 1 commit
  8. 14 Jul, 2016 1 commit
  9. 13 Jul, 2016 2 commits
  10. 10 Jun, 2016 3 commits
  11. 08 Jun, 2016 3 commits
  12. 06 Jun, 2016 4 commits
  13. 01 Jun, 2016 3 commits
  14. 10 May, 2016 3 commits
  15. 09 May, 2016 1 commit
    • Ulf Hermann's avatar
      QmlProfiler: Add a QmlTypedEvent and extend QmlEvent · 8d15633a
      Ulf Hermann authored
      The QmlTypedEvent is mainly useful to read a generic QmlEvent and
      QmlEventType from a QPacket. QmlEventType has a stream operator to do
      exactly that. QmlEvent also gets further options to store 32-bit data
      in addition to 64- and 8-bit data. Also, with the more generic storage
      layout we can reduce the memory consumption of range events by 50%.
      This comes at the cost of additional memory allocations for non-range
      events, but as non-range events are significantly less frequent than
      range events, this is a good tradeoff. Finally the new storage layout
      lends itself to efficient serialization, which will help when
      developing new storage and transfer formats for QML traces.
      
      Change-Id: I420de68b0142f23c8fb2ca8b329d7ffe69c83fe0
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@theqtcompany.com>
      8d15633a
  16. 04 May, 2016 1 commit
  17. 03 May, 2016 1 commit
  18. 29 Apr, 2016 1 commit
  19. 26 Apr, 2016 1 commit
  20. 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
  21. 06 Jan, 2016 2 commits
  22. 11 Sep, 2015 1 commit
  23. 31 Aug, 2015 1 commit
  24. 08 Jul, 2015 2 commits
  25. 16 Jun, 2015 1 commit