#4949 NORM Never A: Need async searches in Journal

[Zarro Boogs per Child]

#4949: Need async searches in Journal
------------------------------+---------------------------------------------
 Reporter:  Eben              |       Owner:  tomeu         
     Type:  defect            |      Status:  new           
 Priority:  normal            |   Milestone:  Never Assigned
Component:  journal-activity  |     Version:                
 Keywords:  update.2?         |    Verified:  0             
------------------------------+---------------------------------------------
 We are currently triggering searches automatically after a slight delay.
 This is good.  However, for slow typists, this delay can be reached while
 still trying to complete the query string.  This is also good, on one
 hand, because it makes a form of pseudo-incremental search (we want a true
 incremental search, ultimately...).  On the other hand, since the searches
 are preformed synchronously right now, this introduces a lag during which
 the UI is unresponsive and characters typed don't appear on screen, which
 makes the search process feel sluggish and cumbersome.

 There is another case which is perhaps even more annoying which occurs
 when the query string is cleared.  It is correct to return to a default
 state (no filter, showing all entries) when the search string is cleared.
 Unfortunately, right now the act of "clearing" the search also takes some
 noticeable amount of time, which means that if I come to the Journal,
 select the query string, and start typing a new one (implicitly deleting
 the old), I experience a delay of about a second before any of my new
 string begins to appear.

 We could fix the latter problem by doing the clear on the same delay as
 the search is triggered, but both of these problems ultimately require an
 async approach to be done correctly.  Incremental search, in particular,
 requires it.

 I've attached the DS I was working with for testing. I have only 175
 entries, so it's not simply a matter of an overfilled Journal.

-- 
Ticket URL: <http://dev.laptop.org/ticket/4949>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system