#6497 NORM Never A: Current Activity-launch behavior makes Develop problematic

[Zarro Boogs per Child]

#6497: Current Activity-launch behavior makes Develop problematic
--------------------+-------------------------------------------------------
 Reporter:  bemasc  |       Owner:  marco         
     Type:  defect  |      Status:  new           
 Priority:  normal  |   Milestone:  Never Assigned
Component:  sugar   |     Version:                
 Keywords:          |    Verified:  0             
 Blocking:          |   Blockedby:                
--------------------+-------------------------------------------------------
 The Journal currently has the ability to recognize .xo Activity bundles in
 the datastore.  When the user launches one of these bundles, the activity
 is installed in ~/Activities/ , and possibly added to the Activity bar at
 the bottom of the frame.

 A user may start an Activity installed in ~/Activities/ and press view-
 source to create their own modified version.  With Develop, this version
 will be saved as a .xo bundle in the Journal.  When the user launches this
 .xo bundle, it will be installed in ~/Activities/, '''overwriting the
 original Activity'''.

 The only good solution I see is for all non-core Activities to be stored
 in the Datastore, with at most temporary copies made during execution.
 There may be other interim solutions, such as detecting and avoiding name
 collisions.  Until this is fixed Develop will be pretty dangerous.

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