You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is
highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If
there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.

Client Customization Kit (CCK) consists
of a wizard application that allows ISPs and content providers to build
customized Communicator installers for delivery on CD-ROM or by network
download. ISPs can use the wizard to customize Communicator preferences,
and add their own branding elements to Communicator, the CD shell, and
the installer. The output of the wizard is a ready-to-distribute customized
Communicator installer.

The wizard incorporates the most typical
customizations previously performed using three separate tools (Account
Setup Editor, Configuration Editor, and Install Builder) into one consistent
interface that guides the user through the entire customization process.

CCK
Wizard Requirements

Wizard should be easy to use, fast, and stable

First screen must consist of "what you need
to get started" checklist

Sample files provided for all graphics and
animations

List defaults in all fields where applicable

Supplemented by easy to use documentation
(Quick Start Guide) that describes how to create the customized files used
by the wizard

Wizard customizations must match CCK license
agreement

Customizations
That Can Be Performed Using the Wizard

Gather customized files and information

Add your branding

includes CD shell customizations

Customize Communicator

Enter connection settings

Customize and build the installer

For customizations beyond the scope of the
wizard:

the user must edit the .jsc file that the
wizard creates. We will provide a separate hashing utility that user uses
to convert their edited .jsc file to a hashed file.

we must provide the user with a tool (command-line-based
install builder tool?) to build the installer that includes the manually
customized files

The documentation will describe how to make
additional customizations that are beyond the scope of the wizard.

Open issues

The Information Design group is not currently
staffed with a graphic designer, so there's no resource for creating the
sample files that we want to accompany the wizard.

Where do the wizard files (.cfg, .jsc, .ini,
rshell.ini) get stored? They must be accessible to the user.

We need to define the points during the wizard
process where users can manually edit any of the files produced by the
wizard, and then continue the wizard process.

Tour
of User Interface

Screen 1: Welcome

Filename: checklist.ini

Feature

Description

Questions

New button

Creates a new installer
configuration. A dialog will appear so the user can enter a name for the
configuration.

Where do new installer configurations
get saved?

Select an existing configuration
(drop down list)

Lets the user edit an existing
configuration.

Create a Copy

Lets the user create a copy
of an existing configuration and save it as a new configuration. (Works
like "Save As")

Screen 2: Gathering Information

Filename: info.ini

Feature

Description

Questions

CD installer checkbox

If checked, clicking the
"Build Installers" button on last wizard screen will cause a CD-ready installer
to be created. If checked, the "Customizing
the CD Autorun Screen" wizard screen will be displayed. If not checked,
this screen doesn't appear.

Network installer checkbox

If checked, clicking the
"Build Installers" button on last wizard screen will cause a Network-ready
installer to be created.

URL for FTP server's download
directory

Dimmed unless "Network installer"
checkbox is checked. This URL is required for network builds. This URL
is inserted into the config.ini file so that when the setup.exe stub installer
reads the config.ini file, the installer knows where to go to download
the JAR files.

Internet Setup checkbox

If checked, the Internet
Setup module is automatically included in the installer when user chooses
"Build Installers" on last wizard screen.If checked, the "Customizing
Internet Setup" and "Customizing Internet Setup - Points of Presence" wizard
screens will appear.

Lists all Communicator components
that are provided for including in an installer. User can build a Navigator-only
installer by selecting the "Navigator stand-alone" component. Internet
Setup will NOT appear in this list. It is automatically included/ not included
depending on whether the user chose the "Include Internet Setup" checkbox
on screen 2 (Gathering Information).

How are we handling components
that are required to be installed (such as AIM)?

Path to .exe file

no default

Component Description

no default

Size in bytes

no default

Show Summary button

Displays a dialog that contains
a non-editable summary of all the user's inputs to the wizard.

Build Installers button

Displays dialog with progress
bar/status messages as installer creation is in progress.

Screen 11: Installer(s) Completed

Filename: done.ini

Implementation of Online Help

The CCK wizard will offer help for each
wizard screen as well as help for each Show Example image.

Clicking the Help button in a wizard screen
will display a Help window (scrolling text widget implemented via INI file)
that contains information about each topic for that wizard screen. To get
help with creating a file requested by that wizard screen, the user will
click a "How To" button, which opens another Help window that contains
the steps necessary to create the desired file.

Clicking the Help button from a Show Example
dialog will take the user directly to the "How To" Help window with instructions
for creating the file.