Talk:Getting started with extension development

Installing the helloworld.xpi file in the helloworld.zip package does not add a link to the tools menu. (FF 1.0.3/WinXP)

It's clearly stated that you need current trunk build, Firefox 1.1a or later. --asqueella 15:10, 30 Apr 2005 (PDT)

Pb with "Registering your extension in the Extension Manager"

I've created the file {71e95839-6f7e-470d-be54-77012fec6313} as explained containing the single line

/home/marc/fmr/FirefoxTest/helloworld/

(I've tried with and without the trailing "/") and started firefox but I can't see anything of the new extension.

I use firefox 1.0.4 on Linux.

Again, you need one of Deer Park releases. This won't work with 1.0.x, only with Deer Park and Firefox 1.1 or later. --asqueella 13:42, 14 Jul 2005 (PDT)

Package Names

I'm not sure if this is always true, but it was a problem for me. The package name must be in lowercase letters. I didn't know this, and didn't find or read it anywhere. In my chrome.manifest, I kept getting the error of "No chrome package registered for chrome://rtse/content/browser.xul .", which was easily fixed by changing all references of 'RTSE' to 'rtse'. Like I said, I didn't find this anywhere, and I think that this page might be best for it, but I thought I'd bring it up first, and let someone with more experience with extension development tell me if this is right or wrong.

JARing

Should we still be saying that it is recommended? There is a discussion here and it seems that there isn't much of a benefit.

Development of a Seamonkey + Tbird / Seamonkey + Firefox extension

This issue should be addressed. A course we have taken with BiDi Mail UI is a common source dir with preprocessing to build sm,tb source dirs and packaging from the auto-built dirs. Before doing this it was kind of hellish to do every update of every source file twice... see the source here.