#2159 NORM Trial-3: Journal should be the active activity at boot

[Zarro Boogs per Child]

#2159: Journal should be the active activity at boot
---------------------+------------------------------------------------------
  Reporter:  Eben    |       Owner:  marco  
      Type:  defect  |      Status:  new    
  Priority:  normal  |   Milestone:  Trial-3
 Component:  sugar   |     Version:         
Resolution:          |    Keywords:  review?
  Verified:  0       |  
---------------------+------------------------------------------------------
Changes (by Eben):

  * owner:  Eben => marco
  * component:  interface-design => sugar

Comment:

 In general, I think this sounds really logical.  It brings up another
 related issue though.

 Consider the mesh view and the example above.  There is a Write activity
 and a Web activity, both with several XOs grouped around it.  When I close
 the Web activity, I find myself in a state where no activity is active.
 This would be represented on the mesh by my XO leaving the Web group and
 hanging out in space, not associated with any activity.  Only when I
 actually join Write again would my XO go join that group on the mesh.

 This being the case, should we actually institute a pending policy anytime
 that the activity view isn't focused?  If I leave to go to the Journal or
 to the mesh, etc, should my XO temporarily leave its current activity?  Of
 course, we're still not sure what granularity this type of update has in
 mesh view;  I might only broadcast my status every couple of minutes.
 Still, what do you think about this in terms of the mesh and active
 activity representation?

-- 
Ticket URL: <http://dev.laptop.org/ticket/2159#comment:12>
One Laptop Per Child <http://laptop.org/>