: K-Meleon Forum
K-Meleon development related discussions.
[quote=guenter] There are three different chrome.dll (plus their xpt). I am too lame to compile but they come from the GRE compilation which can be influenced by parameters. That is what I heard anyway. You would search for it params at Mozilla.org build documentation. I always used/scavanged dll freely available with specific K-Meleon. The files were mostly/normally compiled by Dorian. One set works like SeaMonkey's current dll & xpt (It needs "installed-chrome.txt" and content.rdf and creates a chrome.rdf to register chrome. You can get the files from normal SeaMonkey builds or [b]older[/b] K-Meleon such as 1.02. One set works like Firefox's current dll & xpt, does not need content.rdf and uses installed-chrome.txt to create a file called app-chrome.manifest (the content of that registers chrome for this type of dll). The files are with any [b]current[/b] standard K-Meleon and with dynamically linked Firefox builds. Finally one set is from a [b]NO XUL experiment[/b] that Dorian compiled some time ago. It belongs together with its specific chrome folder and files. The file's name is chrmlite.dll and it has a specific chrome.xpt. You can copy the files over to another K-Meleon install. ([b]=[/b] You can use all three chrome.dll with each K-Meleon, they can be transfered) To change what K-Meleon uses You change(e.g.copy from another K-Meleon) the chrome.dll and xpt in components folder, delete compreg.dat and xpti.dat so that K-Meleon recreates them and by that registers the new files. It is easiest to use the complete chrome folder that belongs to the specific chrome.dll. It took some time to debug the chromes to the current level. The first NX chromes crashed on Java applet pages and had no about: plugins. With some K-Meleon versions the xpt are joined into a big K-Meleon.xpt. That is no good to scavenge files :P. But You can get the separate NX files e.g. from K-MeleonCCFME0.09Beta1.[/quote]
K-Meleon forum is powered by