XUL:XUL Application Packaging: Difference between revisions

Line 13: Line 13:
=== application.ini ===
=== application.ini ===


More info coming...
This file follows the standard format for a Windows INI file. It is currently defined as having two sections, <tt>App</tt> and <tt>Gecko</tt>. The fields for each section are explained in the sample below.
 
<div class="example" title="application.ini - xulapp package information">
<pre class="code">
[App]
;
; This field specifies your organization's name.  This field is recommended,
; but optional.
Vendor=MyOrganization
;
; This field specifies your application's name.  This field is required.
Name=MyApplication
;
; This field specifies your application's version.  This field is optional.
Version=0.1
;
; This field specifies your application's build ID (timestamp).  This field is
; required.
BuildID=2005041816
;
; This field specifies a compact copyright notice for your application.  This
; field is optional.
Copyright=Copyright (c) 2005 MyOrganization
;
; This ID is just an example.  Every XUL app ought to have it's own unique ID.
; You can use the microsoft "guidgen" or "uuidgen" tools, or go on
; irc.mozilla.org and /msg botbot uuid.  This field is optional.
ID={3b2b4f0c-b8e1-4b13-89a6-b5d17523a7e1}
 
[Gecko]
;
; This field is required.  It specifies the minimum Gecko version that this
; application requires.  Specifying 1.8 matches all releases with a version
; prefixed by 1.8 (e.g., 1.8a4, 1.8b, 1.8.2).
MinVersion=1.8
;
; This field is optional.  It specifies the maximum Gecko version that this
; application requires.  It should be specified if your application uses
; unfrozen interfaces.  Specifying 1.8 matches all releases with a version
; prefixed by 1.8 (e.g., 1.8a4, 1.8b, 1.8.2).
MaxVersion=1.8
</pre>
</div>


== Launching a XUL Application ==
== Launching a XUL Application ==
16

edits