1. 17 Apr, 2019 1 commit
  2. 08 Mar, 2019 1 commit
  3. 30 Aug, 2018 2 commits
  4. 14 Nov, 2017 1 commit
  5. 10 Oct, 2016 1 commit
  6. 20 Mar, 2016 1 commit
  7. 04 Mar, 2016 1 commit
  8. 30 Oct, 2015 1 commit
  9. 26 Aug, 2015 1 commit
  10. 24 Aug, 2015 1 commit
  11. 19 Aug, 2015 4 commits
  12. 06 Aug, 2015 1 commit
  13. 04 Aug, 2015 1 commit
  14. 08 Apr, 2015 1 commit
    • chriadam's avatar
      [libcontacts] Run tests with privileges · 96732850
      chriadam authored
      The contact cache provided by libcontacts is intended for use by
      privileged applications only.  Its functionality does not make sense
      for non-privileged clients, and cannot be tested correctly when
      run in non-privileged mode.
      96732850
  15. 06 Mar, 2015 1 commit
  16. 05 Mar, 2015 1 commit
    • mvogt's avatar
      [libcontacts] Some scripts imply name token ordering · f4c2e52e
      mvogt authored
      For a specific set of character scripts, if a contact's first and last
      names are entirely composed of that script, then that (most likely)
      implies a cultural ordering for given/family name tokens that should
      override the device setting.
      f4c2e52e
  17. 16 Feb, 2015 1 commit
    • chriadam's avatar
      [libcontacts] Improve vCard contact import API · 813eafc0
      chriadam authored
      This commit improves the SeasideImport API by allowing clients to
      specify their own SeasideContactBuilder implementation when
      converting the list of Versit documents into storage QContacts.
      
      The SeasideContactBuilder allows the client to parametrise things
      like the contact filter used to determine the subset of mergable
      contacts, the merge strategy to use, and so on.
      813eafc0
  18. 12 Feb, 2015 1 commit
    • Richard Braakman's avatar
      [performance] Avoid resolving addresses multiple times · 4bfe8804
      Richard Braakman authored
      Parts of commhistory (GroupManager) will send a stream of
      resolve requests with many duplicates. This used to be
      tolerable because requests were handled slowly in the
      event loop, but now that they have higher priority it has
      become a problem.
      
      I went for the simple solution of ignoring requests that
      are identical to still-active requests (same uids, same
      listener, same requireComplete flag). It's not optimal (we
      could combine more requests into the same backend query if we
      tried), but it solves the problem without adding a lot of
      bookkeeping.
      4bfe8804
  19. 04 Feb, 2015 1 commit
  20. 01 Dec, 2014 1 commit
  21. 21 Oct, 2014 1 commit
  22. 17 Oct, 2014 1 commit
    • Richard Braakman's avatar
      [performance] Schedule resolveAddress immediately · e2ab0615
      Richard Braakman authored
      resolveAddress requests are done with one query at a time, in
      order to correlate the results with the looked-up addresses.
      Doing them sequentially via UpdateRequest events added a lot
      of overhead in the form of coordination between threads.
      
      This commit creates a dedicated QContactFetchRequest for each
      resolveAddress call, so that the events for starting them can
      arrive all together in the backend thread and the events
      announcing the results can arrive all together in the UI thread.
      They will still be processed sequentially, but this change cuts
      out the delay between finishing one request and starting the next.
      
      In tests with 10k contacts and a recent contacts list with limit=20,
      this reduced the resolve time from 1s to 0.3s.
      e2ab0615
  23. 15 Oct, 2014 2 commits
  24. 17 Sep, 2014 1 commit
  25. 12 Sep, 2014 1 commit
    • Richard Braakman's avatar
      [libcontacts] make sure UpdateRequest processing continues · ff84e74f
      Richard Braakman authored
      The logic for scheduling UpdateRequest events broke down when
      m_contactsToAppend went empty during a fetch request; even though
      more contacts were coming in through contactsAvailable, no more
      UpdateRequest events would be scheduled until the whole request
      was complete.
      
      Fixed by making m_updatesPending the definitive flag for whether
      there is an UpdateRequest event on the queue, rather than leaving
      it on during the whole fetch request.
      
      This change is safe because the flag was only inspected by the
      requestUpdate() helper and had no side meanings. Now all
      UpdateRequest event scheduling goes through requestUpdate().
      ff84e74f
  26. 26 Aug, 2014 1 commit
  27. 31 Jul, 2014 2 commits
  28. 30 Jul, 2014 1 commit
  29. 22 Jul, 2014 2 commits
  30. 01 Jul, 2014 1 commit
  31. 30 Jun, 2014 1 commit
  32. 19 Jun, 2014 2 commits