K-Meleon :: Extensions

Extensions : K-Meleon Forum

All about K-Meleon extensions.

Goto: Forum List•Message List•Search•Log In

Your Name:
Subject:

Help information

[quote=guenter]
[quote=mouse]

[quote=guenter]
5.) K-Meleon has no XUL URLBar that You can color or call easily. It is C++ and only Dorian programms c++. No idea how and if You can do it.
[/quote]
Pity. I guess it will need to be a pop up window or 'bubbble' or something then, or writing text maybe next to the padlock. Is footer accessible? Can you ask for a border colour change, or a border to flash outside the page border. Is there any documentaion that says what functions exist?

Still not sure what I should edit. Sound like its the .xul files in the JAR - is that where you put the window calls you refer to in the first post?
[/quote]

I found something [url=http://kmeleon.sourceforge.net/forum/file.php?9,file=466,filename=FlashblockButton.zip]FlasblockButton extension with the little icon bar by desga2.[/url] It changes icons to show the state of a pref. Could You perhaps adapt that idea? You have experience with programming and maybe Your extension uses states of prefs?

Exactly You edit the files in ./chrome/*.jar/content usually starting with the XUL file that is used by K-Meleon e.g. to change the options or to show a state until it works = K-Meleon ErrorConsole shows no more errors and the XUL window does what You want.

JarTester is used to start such XUL files on the fly to see what they do and to find what errors they raise. You follow the messages of/on the ErrorConsole to the point where execution stops with an error. Fix it & start again.

[quote=mouse]
and sorry for all the questions. Not sure if this stuff is documented anywhere, else I would try that first. [/quote]

Absolutely no need to be sorry. You are trying to create something that ALL can use later = ME TOO! :)

Detailed "How to hack Firefox Extensions" have been described several times - there should be threads.

In a nutshell since You already solved the initial steps alone.

Unpack, drop files into the right K-Meleon folder, if needed delete the 2 ./components/*.dat, fix paths of ./chrome/manifest to work in ./K-Meleon/chrome, start XUL files in ./*.jar/content/ to find which XUL file(s) You need to start the extension & which are used by the other XUL files, find thrown errors in XUL and JS files with the help of Console, fix the errors as good as You can. Common errors: reference to Firefox chrome styles or XUL -> comment out or redirect to K-Meleon chrome or include and reference Firefox files e.g. browser.CSS. JS errors: fix if You can - comment out sometimes helps.

[b]IF[/b] You get Your extension to run, You create a kmm that starts the extension, toggles a pref... and last not least You post/adertise it and its download place in Form :D

p.s. I finished the finding & update of the 2 keys in the toolbars.cfg of 150+ skins and some other changes in as many *.nsi and txt files faster than I though. It is uploaded already. Found and used a tool that more or less helped to automize  the job :)
http://kmeleon.sourceforge.net/forum/read.php?10,112251,112251#msg-112251[/quote]

K-Meleon forum is powered by Phorum.