GoogleCodeIn2012/End-user-mods

From Sugar Labs
< GoogleCodeIn2012
Revision as of 11:02, 19 November 2012 by Walter (talk | contribs) (Created page with ";Background: We have an existing mechanism for duplicating and modifying Sugar activities: a copy of the bundle can be creaed in ~/Activities, where it can be modified by the ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Background
We have an existing mechanism for duplicating and modifying Sugar activities: a copy of the bundle can be creaed in ~/Activities, where it can be modified by the end user. We also have a mechanism for viewing the Sugar toolkit source, but no such convenient way for making changes without risking messing up the system. While it should be easy enough to make a duplicate copy in the user's home directory, and to change the Python paths to use the modified code, we need some mechanism -- presumably at boot -- to choose which version to run: the installed version or the modified version.
Task
Design a mechanism for making end-user modifications to the Sugar toolkit (and possibly Sugar itself).
Contact
Sugar Developer Team
Retrieved from "https://wiki.sugarlabs.org/index.php?title=GoogleCodeIn2012/End-user-mods&oldid=84143"