Brian King wrote:
> Stefano Mazzocchi wrote:
>
>> In fact, I just committed to svn a new extension that I called "firefox
>> tracer" (deerpark ready) that is pretty much the event-handling
>> mechanism of greasemonkey (but without the rest) along with the simplest
>> of our XPCOM+JavaScript+Java components (nsInfoUtil).
>>
>> [find it at http://simile.mit.edu/repository/tools/firefor-tracer/]
>>
>> Everything is traced to every little piece of XPCOM detail and dumped on
>> the console (not the javascript console! the stdout console!, makes it
>> much easier to interact with command line tools like grep/wc/sed and the
>> like.
>
>
> Correct URL: http://simile.mit.edu/repository/tools/firefox-tracer/
>
> Looks like a nice tool. I'm going to try it out. Is there a link to an XPI?
no, I haven't produced an XPI yet.
Went back to take a look, wow, I know a lot more than that now, I should
cleanup that code.
>> I also found a way to reload both xul *and* xpcom components without
>> having to restart the browser, my productivity increased 20 times!! :-)
>>
>> [more on this later]
>
> I'm curious about the XPCOM part.
So, it turns out I was wrong. I can reload the chrome registry
programmatically, but not the xpcom components, I have to restart the
system and touch the folder.
--
Stefano Mazzocchi
Research Scientist Digital Libraries Research Group
Massachusetts Institute of Technology location: E25-131C
77 Massachusetts Ave telephone: +1 (617) 253-1096
Cambridge, MA 02139-4307 email: stefanom at mit . edu
-------------------------------------------------------------------
Received on Thu Sep 01 2005 - 20:01:35 EDT