#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                 |  
-------------------------------+--------------------------------------------
Changes (by cjb):

 * cc: rwh (added)


Comment:

 Replying to [comment:31 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).

 Ivan thinks that this is an appropriate in the "medium-term", and the
 Sugar team thinks it's better than the view-source-only solution in #5475,
 because it makes both "launch ebook from web" and "view source" work
 consistently with the same piece of code.

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