Talk:Custom Toolbar Button
From MDC
Note that there is an article, Creating toolbar buttons, that covers only actually adding a toolbar button using an overlay. The basics are explained in Building an Extension. It might make sense to link to them. --Nickolay 04:43, 23 December 2005 (PST)
Yes, I'll do that. Thanks for the reminder. --Rod Whiteley 05:52, 23 December 2005 (PST)
Thanks - this is the best tutorial I've come across so far - having the file names specified with the complete code section for that file is perfect, and couldn't be easier to follow.
I tried localizing the Custom Button that I'd made, and that worked. Then I tried packaging the \content\, the \skin\ and the \locale\ folders up into a jar and now my extension is broken. I've started from scratch 3 times now and for whatever reason, it's broken and I'm stumped!
I would love to see the Custom Toolbar Button tutorial continue on to "Now let's localize it", and then on page 3 of the tutorial, something like "Now let's package it up like the pros".
A complete tutorial like this would encourage new extension developers like myself to make extensions that can be localized by people around the world. And the more people around the world use Firefox and give feedback (even if it's in 'broken'-English), the more extensions are likely to improve, and be developed. For someone in some far-away country may be inspired to create their own extensions and make them available to also be localized into English. See, it can work vice-versa :o) .. And it starts here. --RenegadeX 23:52, 11 February 2006 (PST)
Yes, my intention was to design a very simplified structure that is easy for readers to make. I am pleased that this worked for you.
But you are also right—the structure is so simplified that it does not support locales or themes in the normal way. I hoped that more advanced tutorials would cover these topics.
I think your ideas for extending this tutorial are interesting. I'll think about writing some more pages.
To get help with your broken extension, I think the best place is the forum, the first link on the Extensions:Community page here.
It sounds like the breakage happened when you made a jar. I wonder if your chrome.manifest points to the jar correctly. Sometimes the JavaScript console (Tools – JavaScript Console from the menu bar) displays error messages that can help.
-- Rod Whiteley 03:00, 12 February 2006 (PST)