Hi, I've been documenting logging for sugar recently and would be very interested in any standardization of logging, so please keep me posted. I've documented roughly the process that already exists for python standard logging if people want to write to log files in sugar (see http://wiki.laptop.org/go/Python_Standard_Logging_in_Sugar). Right now, I instruct developers to just go ahead and create their own custom handlers and formatters. If we want more security in terms of where logs go, I think having an entryin the .info file coupled with a standard api in the sugar.logger package (which is right now just a minimal set of code) might be most appropriate. This might allow users to then look at logs more easily throgh the Log activity, if there is some known place where logs go.
Thanks Faisal On Wed, Jul 9, 2008 at 7:50 AM, Eben Eliason <[EMAIL PROTECTED]> wrote: > On Tue, Jul 8, 2008 at 6:13 PM, Michael Stone <[EMAIL PROTECTED]> wrote: > > It appears that logs posted in the Log Activity go, by default, to > > > > olpc.scheffers.net/olpc/submit.tcl > > Of interest, recent discussion on IRC discussed the possibility of > providing a mechanism for getting logs to "the right place" more > easily. Specifically, it might be possible to add a field to the > .info file so activity developers can indicate where logs should wind > up. Of course, there are security/privacy concerns (and of course > spam concerns), especially if we want kids producing these activities. > Any thoughts on how we could do this sanely? > > - Eben > _______________________________________________ > Devel mailing list > [email protected] > http://lists.laptop.org/listinfo/devel >
_______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
