>It is the newsgroup netscape.public.dev.xul (I'm sure there's a mail >gateway too, but I don't know the alias). I'm sorry about the >abbreviation (this NG is known as npm.xpcom).
No worries - & sorry for being OT, I am a bit lost at the mo'. I hope continuing/ending this thread here is OK, so I can avoid repeating the same stuff elsewhere - if there are objections I'll leave 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? > >XPCOM is the "core" object model that allows everything to happen. You >will be using XPCOM, whether you implement your toolbar code is JS or >C++, but this NG is mainly for core-level problems like registering >components. Given my intentions, is it possible to *explicitly* avoid using XPCOM in favour of a scripting language like JS? (Even if the script implicitly runs using XPCOM objects.) >> 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 > >It should be mydir/ not mydir/myxul.xul Try doing that edit, >and then >remove [mozilla]/chrome/chrome.rdf . The chrome registry will rebuild >the chrome.rdf cache from the installed-chrome.txt file. Followed the instructions to edit / remove files. (also removed chrome.rdf temporarilty from ....\Application Data\Mozilla\Profiles\default\v961015s.slt) After running mozilla again, chrome.rdf does not appear... is there another step involved (other than rebuilding the thing from scratch?) >Do you know how overlays work yet, matching the ID of the overlayed >document and the overlay doc? If not, see the xulplanet.com >XUL tutorial >(there is a section near the end on overlays and dynamic overlays). Have read this, thanks - I get so far - when I open my .xul file from the Browser file window, I get a duplicate copy of the navigator toolbars with my own toolbar above. I'm assuming once it gets installed as an overlay both problems will go away. >This would probably be a lot easier for you if you didn't worry about >dynamic overlays yet. Build mozilla for yourself using flat chrome (or >symlinked chrome on *nix), and manually edit navigator.xul with an ><?xul-overlay?> directive. When you build mozilla yourself, >stick to a >release version; the source for 1.5 would be a good bet, or the 1.6 >branch which is pretty stable. Thanks for the advice - though from the outside it doesn't sound less complicated! As always, MTIA Tony _______________________________________________ Mozilla-xpcom mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpcom
