Configuring Firefox for Chrome and a Server - Package Registration (Page 3 of 4 )
Every time the Firefox browser launches, its framework looks for any file with an extension of .manifest to inform it of the chrome content packages, skins, or locales that need to be loaded. To inform Firefox of our NewsSearch application, we will use a text editor to create a line for a file named localApps.manifest (any unique filename with a .manifest extension will do) and save it in Firefox’s chrome directory:
A user can communicate to a server using several models, including a XUL application that runs locally while obtaining needed server information through asynchronous HTTP requests. Using this approach, the local application is in complete control of the user interface, with the server providing only textual information in response to requests. Here are the steps for implementing this model:
Configure a web server.
Install a scripting language to provide logic that manages communications with a client application.
Implement the communication connection between the application and the server.
Add a database on the server to communicate with the scripting language.
Figure 4-5. OS X and Windows presentation of newssearch.xul (after simulated login)