#3019 HIGH Trial-3: PATCH: Optimize get_activities by making it async

[Zarro Boogs per Child]

#3019: PATCH: Optimize get_activities by making it async
---------------------+------------------------------------------------------
  Reporter:  J5      |       Owner:  tomeu               
      Type:  defect  |      Status:  new                 
  Priority:  high    |   Milestone:  Trial-3             
 Component:  sugar   |     Version:                      
Resolution:          |    Keywords:  optimization review?
  Verified:  0       |  
---------------------+------------------------------------------------------
Comment (by J5):

 Hiding complexity is a poor reason for not adding the async operations.
 The public API is still backwards compatible and some people may wish to
 use async calls for all D-Bus calls.  It is a good habit to get into
 actually.  Letting people know this is a network operation and could
 block, even if it is unlikely, makes sure programmers can make informed
 decisions.  Also as you see using the async API isn't all that complex.

 BTW, on marco's question - most of what I think is happening is a guess of
 where to look but I think the time isn't in passing the list so much as
 iterating over it to create objects from dicts and then iterating again to
 display them.  I'll have more info as I start profiling after we enter
 gtk.main.  There is a big problem with this though since the python
 profiler needs to execute the command it is profiling instead of giving me
 the ability to start and stop the profiler at whim.

-- 
Ticket URL: <https://dev.laptop.org/ticket/3019#comment:8>
One Laptop Per Child <http://laptop.org/>