[Bugs] #535 UNSP: Expose Journal, Home, Group, Neighborhood, & Frame Sources

[Sugar Labs Bugs]

#535: Expose Journal, Home, Group, Neighborhood, & Frame Sources
------------------------------------------+---------------------------------
    Reporter:  FGrose                     |          Owner:  tomeu            
        Type:  enhancement                |         Status:  new              
    Priority:  Unspecified by Maintainer  |      Milestone:  0.90             
   Component:  sugar                      |        Version:  Git as of bugdate
    Severity:  Unspecified                |       Keywords:                   
Distribution:  Unspecified                |   Status_field:  Needinfo         
------------------------------------------+---------------------------------

Comment(by walter):

 Note that the Sugar Toolkit source is now accessible from the Sugar
 activities View Source toolbar. When doing that work, I added access to
 jarabe from the Journal's Frame entry (http://lists.sugarlabs.org/archive
 /sugar-devel/2011-May/031511.html). That code didn't survive design review
 as it was a bit too much of a special case, but it would be pretty easy to
 do for all of the Sugar components, including View Source itself.

 One thing we need to be able to do in addition is some sort of cloning as
 per the Activity bundles. We could modify sys.path to look in ~ for Sugar
 modules but if the user makes a mistake, we need a simple way to recover:
 perhaps something as simple as if ~/jarabe exists, then prompt the user on
 launch as to whether to run Sugar from ~ or /usr/lib/python/site-packages

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/535#comment:7>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system