Topics Man is not wrong, you can't "patch" the Mozilla chrome directly. You can "overlay" parts of it (see the XUL experts) or you can replace it completely.
You can also work with the appropriate module owners to add hooks into the standard UI you can use if overlays of the current UI are insufficient. -Dan Veditz shadows wrote: > Have you figured out how to do it yet? I have the same problem... > > "Topics Man" <[EMAIL PROTECTED]> schrieb im Newsbeitrag > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > >>Hello all, >> >>Suppose that: >> >>1) you are developing an application which you intend to install with >>XPI. >> >>2) this requires some small modifications to existing Mozilla chrome >>files, eg. adding a couple of entries to the standard Mozilla menus, >>adding a line or two of JS to standard Mozilla js files, and so on. >> >>As far as I can see, you cant do this. You can only completely overwrite >>the standard Mozilla files, which means you have to maintain/install >>your own patched copies and deal with all the change control issues >>which this raises. >> >>Or am I wrong? >> >>I am looking at this from the perspective of the MultiZilla project >>(http://multizilla.mozdev.org). MultiZilla sure comes with its own >>distinct chrome files containing new functionality, but it also needs to >>patch the existing Mozilla chrome files (like in the above examples) to >>allow them to work. >> >>Is there a recommended way to achieve this? >> >>Examples of what we need to achieve on MultiZilla installation are: >> >>1) add new commands (menus, keystrokes) to the Communicator UI to >>control the new functionality >>2) insert hooks into Communicator JS to allow us to handle various >>events (eg. user clicks on a link in the content) >>3) etc. >> >>Cheers, >>Chris >> >> > >
