Thanks for the code & advice! The learning curve continues to resemble an overhang ...
>Please use npd.xul for this stuff (or npm.xpinstall). This has >little/nothing to do with XPCOM. I'm confused by this - what is npd.xul? I searched the mozilla website but have not found it. Also, I'm trying to connect the toolbar to some funky C++ code - which will require XPCOM. Is it the case that I can make an XPCOM widget "listen" to the buttons on the dynamic overlay? Basically the widget needs to load, and store internally, a file local to the user's system and modify web page contents according to that. I began on the XPCOM track believing this was the only way to put new buttons and toolbars into the browser - was this a misunderstanding of mine? If it can be done in Javascript I think this may be easier (unsure what reaction my boss will have to making the widget open source though.) Have added the following as per your advice... [mozilla]/chrome/mydir/myxul.xul [mozilla]/chrome/mydir/contents.rdf and to installed-chrome.txt - content,install,url,resource:/chrome/mydir/myxul.xul I've experimented with variations on this (like ending the above line at "mydir/" or referring to the rdf file instead) So far... with none of these variations have I seen the toolbar in a browser, and with some I have managed to kill mozilla completely! Any help is much appreciated as always! Tony _______________________________________________ Mozilla-xpcom mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpcom
