While you are developing the extension, there are two ways you can make Thunderbird load it so you can test it as you go. You can either put the folder with the extension files directly into Thunderbird's extensions folder, or you can put a file there that tells Thunderbird where your extension is located. (In step 7 you will learn how to package an .xpi file for distribution and installation.)
To find the Thunderbird extension folder, navigate to Thunderbird's profile directory and open the extensions/ folder. Depending on the operating system it will be in one of the following locations:
Using a text file to reference your extension files (recommended):
- If you are developing your extension in a different folder (for example "...\My Documents\Code\Thunderbird Extensions\firstname.lastname@example.org\"), then you can create a text file in the extensions/ folder to point to it. The name of the text file must be exactly the same as the value of
<em:id>from install.rdf. In our case the file will be named:
- The file must contain a single line with the absolute path of the extension. The folder that is referenced must be the same as the value of
C:\Documents and Settings\<user name>\My Documents\Code\Thunderbird Extensions\
Putting the extension file directly into the extensions folder (alternative):
- After you have opened the extensions/ folder, create a sub-folder with the name of your extension. This name must be exactly the same as the id of the
<em:id>field in the install.rdf file. In our case the folder will be named:
email@example.com/. Depending on the format of your id, the folder name may also be a GUID.
Now you can start Thunderbird. Thunderbird will detect the extension and try to load it.
See Setting up extension development environment for how to set up a developer profile and enable debugging features.
You can now go back and make changes to the .
xul file. When you close and restart Thunderbird they should appear.