[Sugar-devel] heads up re proposed View Source changes
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
Re: [Sugar-devel] heads up re proposed View Source changes
Hi Walter--it may be best to discuss this during an IRC session since I'm having difficulty understanding the functionality... :) Maybe we could schedule a review for this Sunday? Christian On Mon, Jun 6, 2011 at 11:40 AM, Walter Bender wrote: > 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 > > -- anyth...@christianmarcschmidt.com 917/ 575 0013 http://www.christianmarcschmidt.com http://www.facebook.com/christianmarcschmidt http://www.linkedin.com/in/christianmarcschmidt http://twitter.com/cms_ Skype: christianmarcschmidt ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] heads up re proposed View Source changes
On Mon, Jun 6, 2011 at 10:47 PM, Christian Marc Schmidt < christianm...@gmail.com> wrote: > Hi Walter--it may be best to discuss this during an IRC session since > I'm having difficulty understanding the functionality... :) Maybe we > could schedule a review for this Sunday? > Sure. I will be tied up in the AM Sunday -- doing a charity bike ride, but will try to get on line as soon as I can. -walter > > Christian > > > On Mon, Jun 6, 2011 at 11:40 AM, Walter Bender > wrote: > > 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 > > > > > > > > -- > anyth...@christianmarcschmidt.com > 917/ 575 0013 > > http://www.christianmarcschmidt.com > http://www.facebook.com/christianmarcschmidt > http://www.linkedin.com/in/christianmarcschmidt > http://twitter.com/cms_ > Skype: christianmarcschmidt > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
