1. 24 Feb, 2017 40 commits
  2. 15 Aug, 2016 40 commits
  3. 14 Jul, 2016 40 commits
  4. 10 Jun, 2016 40 commits
  5. 23 May, 2016 40 commits
    • 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
      later.
      
      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
      models.
      
      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>
      4a1e5a63
    • 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>
      1e8996b4
    • Ulf Hermann's avatar
      QmlProfiler: Load the timeline model data event by event · 5ba6f04d
      Ulf Hermann authored
      All the models do the same thing when loading the data: They iterate
      the list of events, determine for each one if they accept it, and if
      so, they load it. After the list has been fully loaded, they do some
      finalization. This can be centralized, and ultimately we won't need to
      expose the central QVector<QmlEvent> for that anymore.
      
      Change-Id: Ia82facfdc3968200bbec323a02f2fcc02ac44e9e
      Reviewed-by: Joerg Bornemann's avatarJoerg Bornemann <joerg.bornemann@qt.io>
      Reviewed-by: Ulf Hermann's avatarUlf Hermann <ulf.hermann@qt.io>
      5ba6f04d
    • 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>
      1093be04
  6. 04 May, 2016 40 commits
  7. 03 May, 2016 40 commits
  8. 30 Mar, 2016 40 commits
  9. 19 Jan, 2016 40 commits
  10. 16 Nov, 2015 40 commits
  11. 02 Jul, 2015 40 commits
  12. 16 Dec, 2014 40 commits
  13. 15 Dec, 2014 40 commits
  14. 21 Nov, 2014 40 commits
  15. 09 Oct, 2014 40 commits
  16. 29 Sep, 2014 40 commits
    • Ulf Hermann's avatar
      QmlProfiler: rename "eventId" fields to "typeId" and "selectionId" · 38f4d6a5
      Ulf Hermann authored
      The convention is now that selections are the rows in the expanded
      timeline, "types" are the types in the QmlProfilerDataModel, and
      events are the single boxes in the timeline. Thus, the event view
      shows only types and for consistency the V8 view does so, too.
      
      Having eventId as synonym for "type index" and "event index" as
      actual index into the list of events is confusing.
      
      Change-Id: I6b7c4c3f1ab0a8b71c511de52ab296a2e91cf5f0
      Reviewed-by: default avatarKai Koehne <kai.koehne@digia.com>
      38f4d6a5
  17. 15 Sep, 2014 40 commits
  18. 10 Sep, 2014 40 commits
  19. 26 Aug, 2014 40 commits
  20. 24 Jun, 2014 40 commits
  21. 17 Jun, 2014 40 commits
    • Ulf Hermann's avatar
      QmlProfiler: get rid of hash strings · fea6580c
      Ulf Hermann authored
      Using strings to identify equal events is terribly inefficient. By
      keeping a global list of event types we can assign each event a
      numerical type index and use that to compare them.
      
      We can also avoid excessive string copying and data duplication by
      referring to the global type list where event type information is
      needed.
      
      Task-number: QTCREATORBUG-11823
      Change-Id: I837bd5d0f5395b0003002ef8dd278fb27679c65d
      Reviewed-by: default avatarKai Koehne <kai.koehne@digia.com>
      fea6580c
    • Ulf Hermann's avatar
      QmlProfiler: Remove SingleCategoryTimelineModel · c7c4be9c
      Ulf Hermann authored
      All models are single-category now, so we can merge that into the base
      class.
      
      Change-Id: I4eab43ac2b4a77402121f004097e51a29b379aa4
      Reviewed-by: default avatarKai Koehne <kai.koehne@digia.com>
      c7c4be9c
  22. 16 Jun, 2014 40 commits
  23. 11 Mar, 2014 40 commits
  24. 19 Feb, 2014 40 commits
  25. 18 Feb, 2014 40 commits