#4909 BLOC Update.: Activities shoud be able to launch other activities

[Zarro Boogs per Child]

#4909: Activities shoud be able to launch other activities
-------------------------------+--------------------------------------------
  Reporter:  marco             |       Owner:  tomeu              
      Type:  defect            |      Status:  new                
  Priority:  blocker           |   Milestone:  Update.1           
 Component:  journal-activity  |     Version:                     
Resolution:                    |    Keywords:  rainbow-integration
  Verified:  0                 |  
-------------------------------+--------------------------------------------

Comment(by cscott):

 ok, conversation with cjb, erikos, and m_stone seems to indicate that a
 reasonable stop-gap design is to provide a way for an application to ask
 that we zoom to the journal with a particular object id selected (ideally,
 we'd zoom to the detail page for that object).  the user is then just one
 click away from launching it in an appropriate activity, and the click
 happens in a 'trusted' bit of code (the journal).

 Alternatively, among the bitfrost security properties for an activity
 should be two bits: "i can be trusted to launch other activities" and "i
 am safe to launch with arbitrary content".  Unsigned untrusted activities
 have neither of these bits.  We enable 'i am safe to launch' on Read, and
 'i can be trusted to launch' on Browse.  View source, in this vision, is
 handled by sugar-shell sending a message to the activity and getting back
 an datastore object id which is supposed to represent the source.
 Malicious programs returning evil bits of 'source' to view are prevented
 by the 'i am safe to launch with arbitrary content' flag of activities.

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