Jason Bassford wrote: > I thought of just replacing the whole .jar myself - but the only > problem with that is that you'd end up with version inconsistencies. > Your installer routine would only be definitely usable with the > version of Mozilla that the .jar you're using came from...
Your idea to modify individual files has no guarantee of a longer life, but of course depends on what bits you're modifying. Your mods have a better chance at a long life in un-owned, forgotten, sleepy bits of the code -- but if part of the code is un-owned and needs improvement why not work with the Mozilla community to get your changes into the official repository. But you should really look into overlays. That's the approved way to modify chrome. There are limits to what's possible, and you may have to coordinate with the chrome owner of the bits you want to overlay to add a hook for you, but in the end it's much more supportable. -Dan Veditz
