Please see: http://wiki.sugarlabs.org/go/Design_Team/Proposals/Toolbars/View-Source_Enhancements
There are a series of patches I sent today to sugar-devel you could apply if you are interested in trying it. My outstanding questions (above and beyond the ones you may have): * The graphical overlay I use for indicating that an activity is a copy is not as clear as I'd like; * I don't include a mechanism for copying Sugar source since I am not sure how best to deal with error recovery (I could copy site_packages to ~ and set the Python sys.path to look in ~ before looking in /usr/lib/python, but if the user makes a mess of their Sugar environment, how should they recover? In the case of Activities, they have the original and the copy.) * I didn't include /usr/share/sugar in the Sugar view source but should probably include at least some of the subdirectories there. regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel