Appstubs Mozilla application stubs.
These files makeup a complete, installable mozilla application. They are meant to ease the development of a mozilla application.

To create an xpi  from in the appStubs directory do:
	zip -r appstubs.jar content locale skin
then do:
	zip -r appstubs.xpi install.js appstubs.jar
The above creates an appstubs.jar and then creates an installable appstubs.xpi
There is an InstallMaker.pl perl script in the application root directory that automates the xpi creation process, works on linux.

So a mozilla application should have the following:
* The root name of the root directory is the name of the application.
* The deafault xul document in the /appstubs/content directory is named as the root directory, 'mozilla -chrome chrome://appstubs/content' points to chrome://appstubs/content/appstubs.xul and this holds true for the /skin/default/appstubs.css and /locale/en-US/appstubs.dtd files

There is an install.js script that is for inclusion in the xpi for this application. It should work unchanged unless you change the directory structure of this application.

There is an 'installed-chrome.txt' file included that can be used to install the live directory for development. When you get your application working then you create an xpi to distribute it.

There are 'mozilla-rebuild-databases.pl' and 'rebuild-databases.sh' to assist in rebuilding the chrome databases when a change is made in the /appstubs/content/contents.rdf file.These work in linux. I don't know if 'mozilla-rebuild-databases.pl' script works in windows or not. Another method of making the overlays.rdf reflect the contents.rdf is to delete the /chrome/chrome.rdf file and the directories under /chrome/overlayinfo, the next time mozilla starts this will be rebuilt and the overlays.rdf will be updated.

There is the 'app-installer' directory that has a webpage with an xpi install tigger to aid distribution of your application.