Skip to content
This repository has been archived by the owner on Oct 12, 2021. It is now read-only.

Commit

Permalink
How to build the output application to execution with xulrunner. We w…
Browse files Browse the repository at this point in the history
…ill review this to make cfx more friendly or add a script to do this.
  • Loading branch information
taboca committed Oct 29, 2010
1 parent cd9736e commit 2cbedb6
Showing 1 changed file with 13 additions and 0 deletions.
13 changes: 13 additions & 0 deletions README.md
Expand Up @@ -12,12 +12,25 @@ ultimate goal is to build your own browser using (mostly) standard web technolog

## Getting Started


1. ./run

or pass an argument for the files located inside the `./ui` directory

2. ./run first_browser/index.html or ./run test_require/index.html

## Background - Use of Addons SDK ( a.k.a. Jetpack SDK )

This is a package and build system and the run script is based on the Mozilla Addon SDK ( http://github.com/mozilla/addon-sdk ). It uses cfx program to dynamically create a new profile, plus, it uses the ./template/app-extension and information fro the ./impl/packages/chromeless to build your application. When it builds, it calls firefox ( or XULRunner ) passing the application.

If you want to see the actual generated output and ship with XULRunner or to launch it directly from XULrunner, you need ( so far til we make it easier ) to call cfx using the "xpi" argument instead the "run" argument.

./impl/bin/cfx -a xulrunner -t ./template/app-extension --static-args {\"browser\":\first_browser/index.html\"} -p impl/packages/chromeless xpi

This will generate an .xpi file. Create a new directory, enter it, unzip the xpi file into this directory, add the ../template/app-extension/application.ini file to it and launch with XULRunner:

xulrunner ./application.ini

## What could go wrong?

In order to work, you probably should make sure you've got ffx 3.6.x
Expand Down

0 comments on commit 2cbedb6

Please sign in to comment.