#3431 HIGH Trial-3: Need to be able to share objects in the mesh, not just activities

[Zarro Boogs per Child]

#3431: Need to be able to share objects in the mesh, not just activities
-----------------------+----------------------------------------------------
  Reporter:  kimquirk  |       Owner:  marco  
      Type:  defect    |      Status:  new    
  Priority:  high      |   Milestone:  Trial-3
 Component:  sugar     |     Version:         
Resolution:            |    Keywords:         
  Verified:  0         |  
-----------------------+----------------------------------------------------

Comment(by Eben):

 Replying to [comment:2 kimquirk]:
 >  * Design team. I talked with Eben and I think we need a way to
 > differentiate activities and objects. Either using visual styling inside
 > the mesh view or doing some sort of overlay (which I think would be
 > cleaner but we would have to evaluate implementation if we go that way).

 Whatever method we choose, I think we need to indicate the distinction
 between collaborations (activities) and objects (their result).  I'm not
 confident that anything we do in the current mesh view will be distinct
 enough, since the implication for objects in that view is that XOs can
 cluster around them eg. they are activities.  Still, in order to get a
 rough implementation of this working sooner than later, I would be content
 to skip the overlay if we can come up with another way of making the
 distinction.

 > Also Eben was thinking to a slightly different way to trigger share from
 > the journal. Anyway we need a solid/agreed design before starting with
 > the implementation.

 I think that we need to make this an action upon the object, rather than a
 change to its state.  To clarify, I mean that we shouldn't be "setting a
 sharing scope" for the Journal entry, since that implies a more persistent
 change.  Instead, what we're really doing is posting a copy of the current
 state of the object itself, much like tacking it to a bboard.  However we
 reveal this in the Journal, we should make it clear that it is tacking up
 a snapshot, and not in any way permanently linking/publishing the file (It
 should be a momentary button).

-- 
Ticket URL: <https://dev.laptop.org/ticket/3431#comment:3>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system