|resources:||Home Mailing List Installation Source Code Members Screenshots|
Use the following procedure to setup a uniform development environment:
- I use java/ant for builds, so install jre or jdk.
- Install ant, set ANT_HOME environment variable and add ant/bin to the Path environment variable, so you can run ant from command line.
- Visit the mozillazine knowledge base and set the FireFox environment to allow debugging messages in the console, etc.
- Follow this procedure to make sure you can open FireFox with a console running, so you will be able to see the 'dump' messages.
- Setup a cvs client, check this page for cvs settings.
- Download the latest source from the source tree.
- Find the 'build.properties' file under the 'leetkey' folder, you will need to modify one property: 'extension_dir'. Set it to wherever the extension's 'chrome' directory is stored on your system (use forward slashes as path seperators only.) For example on a windows machine this line could look like this:
- In the 'leetkey' folder create a new executable script file such as 'make.bat' or 'make.sh' for example that contains the following line: ant update. When you run 'update' target from the build.xml, the leetkey.jar file in the extension chrome directory will be updated with the new one from your current source. This means that in order to test your source, you can just close the browser, run the make script to update the leetkey.jar file and then open the browser.
Obviously you can skip this process and create your own build scripts, here is a zip tool that can be used from command line.
Useful reference links: