1. 12 Jun, 2017 1 commit
  2. 24 Feb, 2017 2 commits
  3. 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>
  4. 15 Feb, 2017 2 commits
  5. 05 Aug, 2016 1 commit
  6. 25 May, 2016 1 commit
  7. 23 May, 2016 4 commits
    • Ulf Hermann's avatar
      QmlProfiler: Make progress widget more expressive · c39ed2a3
      Ulf Hermann authored
      Instead of the progress bar we can now show the number of events we
      have received, and the number of finished finalizers. This should give
      a the user a better idea of what is going on.
      Change-Id: I324fefbe6d5e3c24b080bfbc103c4317fa585215
      Reviewed-by: Joerg Bornemann's avatarJoerg Bornemann <joerg.bornemann@qt.io>
    • Ulf Hermann's avatar
      QmlProfiler: Drive event loading from the model manager · 4a1e5a63
      Ulf Hermann authored
      We want to get rid of the big master list of QmlEvent in
      QmlProfilerDataModel, as that gets very large for longer traces. In
      order to reduce the dependencies on that list we load the events on the
      fly into the child models while they are being received, rather than
      having the child models query QmlProfilerDataModel for the event list
      As the trace client so far only emitted rangedEvent() for complete
      ranges we run into problems with models that need their events sorted.
      The rangedEvent() signals were sorted by end time, rather than start
      time which makes it inconvenient to analyze them in a stack based way,
      for aggregation. This is solved by passing on all the details from the
      trace client to the models, with the QmlProfilerDataModel aggregating
      the type information before having the events dispatched to the child
      Change-Id: I5831a20551f21cf91e27d298a709f604ebd96c3e
      Reviewed-by: Joerg Bornemann's avatarJoerg Bornemann <joerg.bornemann@qt.io>
      Reviewed-by: Ulf Hermann's avatarUlf Hermann <ulf.hermann@qt.io>
    • Ulf Hermann's avatar
      QmlProfiler: Methods for dispatching events by feature · 1e8996b4
      Ulf Hermann authored
      When announcing features models have to provide functions that handle
      events for those features now. The model manager gets a function to
      dispatch events to the models that subscribe to them.
      Change-Id: I3fd80443a68ba264a513d8d53ed473cf072f1dc7
      Reviewed-by: Joerg Bornemann's avatarJoerg Bornemann <joerg.bornemann@qt.io>
    • Ulf Hermann's avatar
      QmlProfiler: Remove detailed progress tracking · 1093be04
      Ulf Hermann authored
      The progress bar in the state widget was rather meaningless. We rarely
      know how many events we expect and it's rather hard to tell how long
      each model will take to process them. Instead, we just show a 0-ranged
      progress bar to tell the user that "something is happening".
      Change-Id: Icb80840d1f0a1538bcf254faa37cbb36e25d342c
      Reviewed-by: Joerg Bornemann's avatarJoerg Bornemann <joerg.bornemann@qt.io>
  8. 10 May, 2016 2 commits
  9. 06 May, 2016 1 commit
  10. 03 May, 2016 1 commit
  11. 30 Mar, 2016 1 commit
  12. 19 Jan, 2016 1 commit
  13. 19 Nov, 2015 1 commit
  14. 11 Sep, 2015 4 commits
  15. 01 Sep, 2015 1 commit
    • Ulf Hermann's avatar
      QmlProfiler: Clean up the state widget · b054fd85
      Ulf Hermann authored
      Ultimately we want this as jobs for the progress manager, but let's
      get the logic right before. The state widget should not estimate
      profiling times and it doesn't have to keep local copies of all the
      state the model and state managers already have. Also, we need an
      additional indication for "waiting for application to send data", as
      that can take significant time.
      Change-Id: I3677dea4b0561bc83a7bc3c196ce0854c5624f12
      Task-number: QTCREATORBUG-12958
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@theqtcompany.com>
  16. 08 Jul, 2015 1 commit
  17. 27 May, 2015 2 commits
  18. 18 May, 2015 1 commit
    • Ulf Hermann's avatar
      Timeline: Remove useless dataAvailable() signals · d71dfa97
      Ulf Hermann authored
      The only thing they did was trigger some QML code that set the zoom to
      10% of the available range. 10% is somewhat arbitrary, so we shouldn't
      have it in the general purpose timeline. Also, we don't really have to
      pass the signal through several connections just to do that in QML.
      The clearChildren() didn't have any effect there as dataAvailable()
      should only happen if the view is already cleared.
      Change-Id: I1813ed37a82fc3fd5c3b7fc02b2afb1dcbcadcfb
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@theqtcompany.com>
  19. 26 Feb, 2015 2 commits
  20. 16 Jan, 2015 1 commit
  21. 21 Nov, 2014 2 commits
  22. 15 Oct, 2014 1 commit
  23. 09 Oct, 2014 1 commit
  24. 15 Sep, 2014 1 commit
  25. 12 Sep, 2014 1 commit
    • Ulf Hermann's avatar
      QmlProfiler: Add EngineControl · b4f336f1
      Ulf Hermann authored
      With EngineControl multiple QQuickViews can be profiled in one
      profiler if they're all running in the same thread. As the QML
      engines are never run in parallel then this results in useful
      Change-Id: I83a34fb81fd466c5cac838b096c1b1f322ded882
      Reviewed-by: default avatarKai Koehne <kai.koehne@digia.com>
  26. 17 Jun, 2014 1 commit
  27. 06 Jun, 2014 1 commit
  28. 02 Apr, 2014 1 commit