BTW, for the record, here's what I've found out so far... * AFAICT you need to manually include the mochikit sources (via <script>s, for example) in your overlay, and be careful to do so in an order that respects dependencies.
* You can add a console object to the window and a log() method to it that passes the argument through to dump(). * You can call LoggingPane.createLoggingPane() a bit after the browser loads (being careful not to call it in the LoggingPane window itself! for example ensuring that document.title doesn't contain "LoggingPane"). Inline display doesn't work. * Wasn't able to get it to work with firebug's console, but didn't try very hard at all. Would be interested in other/better solutions if anyone has them. And, btw, thanks so much for this toolkit! On Dec 4, 12:59 pm, phritz <[EMAIL PROTECTED]> wrote: > Hi there. I'm using Mochikit in a firefox extension and am trying to > figure out the best way to access information that is log()ed. It > doesn't appear that it logs to the js console by default when MK is > loaded in chrome. > > I suppose I can/should Logger.addListener() to hear about messages and > then use the console service to write them out (assuming that's where > I want them to go)? > > Or better yet, perhaps I can hack the logger to log to the web window > the logging bookmarket uses (in regular web pages)? > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
