From 8784bc115b5a7655cf731720a3ed4fbb184bec27 Mon Sep 17 00:00:00 2001
From: "leaf%mozilla.org"
+
+
+
+Chapter 12
+
+
+
+
+
+Advanced Mozilla Customizations
+
+
+After you've run the CCK tool, produced an installer, and made any manual customizations you may require for the CD autorun screen, you can perform additional manual customizations before distributing the installer to your users. This chapter provides an overview of the preferences architecture and the general procedure for manual customization. It also provides detailed, step-by-step instructions for some of the most common manual customizations.
+
+
+This chapter contains these sections:
+
+
+Understanding How Manual Customization Works
+
+
+Understanding How Manual Customization Works
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Understanding the Preferences Architecture
Before You Start
Editing a Configuration File with a Text Editor
Instructions for Common Manual Customizations
+
+
+ +Mozilla is shipped with many preferences and user-interface items preset as "factory defaults." After Mozilla is installed, these settings are stored in special Javascript files called configuration files. +
++ +You can edit configuration files to customize the default settings for your users. For example, you can manually customize: +
++ +To create a customized Mozilla installer by using a combination of the CCK tool and manual customizations, you follow this general procedure: +
++ +For step-by-step instructions describing this procedure more precisely for specific manual customizations, see single change to a JavaScript file, see Instructions for Common Manual Customizations. +
++ + +Understanding the Preferences Architecture +
+
+Factory defaults are set in .js files, which are in turn located in zipped .xpi files in the directory
+
+
+The primary .js file is all-ns.js, which is located in the file browser.xpi.
+
+
+Note: If you make changes to preferences stored (after installation) in the prefs.js file, where the user-configurable customizations are stored, you run the risk of overwriting the bookmarks, address books, and other settings that your users may have set in their existing profiles.
+
+ + +Table 12-1 JavaScript files to edit +
+
+
+Setting a preference in one of the .js files will create a default value that can be changed by the user by choosing Preferences from the Edit menu. Not all preferences are initialized at startup via these .js files. In addition, some settings are stored in RDF files that live in the operating system's directory after the user installs Mozilla. For example, for Windows NT, the path would be:
+
+ + +Important Legal Restrictions +
+ + ++ +The license that ships with the CCK tool imposes restrictions on certain kinds of customizations. In particular, under the terms of the license agreement, you may NOT perform any of the following customizations: +
+
+
+The CCK tool allows you to customize specific aspects of the look and feel of Mozilla. In addition, by editing all.js and other configuration files, you can customize almost any aspect of Mozilla. You'll need to familiarize yourself with the Mozilla user interface and associated preferences to assess how to customize Mozilla for your needs. You'll also need to identify:
+
.xpi file where the configuration file is located in the installation files produced by the CCK tool.
+
++ +More details about names of specific preferences and the configuration files where they are stored will be provided online. See the Mozilla 1.4.1 Client Customization Kit Release Notes for the most current information. XXX - need mozilla.org equiv +
++ +Some Mozilla features or attributes are under user control, but only indirectly. Such features include whether certain toolbars are displayed, and also settings that Mozilla remembers automatically, such as window size and position. Such settings are not "preferences" in the typical sense, because they cannot be set from a user-selected window or dialog box. Instead, these features are referred to as Mozilla "states." +
++ +In addition to the preferences that you can set, you can alter Mozilla configuration settings that are not under direct or indirect user control, such as the items that appear in the Help menu. +
++ + +Editing a Configuration File with a Text Editor +
+
+By editing all-ns.js and other configuration files directly, you can modify Mozilla in a variety of ways. You should use a simple text editor (one that doesn't do any formatting) to modify a configuration file. For example, you can use NotePad for Windows, SimpleText for Mac OS, or vi for X-Motif. If you use a word processor to edit the configuration file, make sure you save the edited configuration file as plain (ASCII) text. If formatted characters are used, the configuration file may not be created correctly.
+
+
+As described above under Understanding How Manual Customization Works, once you have extracted the .js file that you want to modify from the xpi file, you can edit it with a text editor. To do so, you must determine the value type that the preference takes (numeric, string, or boolean) and make the required change to produce the default setting that you want.
+
+ +Important: Don't use Mozilla Composer to edit configuration files. Composer adds characters to the file that can interfere with its use as a configuration file. +
++ + +Instructions for Common Manual Customizations +
+ + +Customizing the Welcome Page +
+ + ++ +The Welcome page appears when the user starts up a new profile for the first time. You may want to customize it so you can provide up-to-date information for new users when they first launch Mozilla. +
++ +Follow these steps to manually customize the URL specified for the Welcome page: +
+browser.xpi into a convenient empty directory.
+
+bin/defaults/pref/all-ns.js.
+
+all-ns.js with a text editor.
+
+bin directory again into a new file called browser.xpi.
+
+browser.xpi file in CCKTool\Configs\my_config\Core\ with the new browser.xpi.
+
+++ + + + + diff --git a/mozilla/cck/CCKDocs/browser_cck.htm b/mozilla/cck/CCKDocs/browser_cck.htm new file mode 100644 index 00000000000..ffab43d7575 --- /dev/null +++ b/mozilla/cck/CCKDocs/browser_cck.htm @@ -0,0 +1,1005 @@ + + + + + + + + +
+
+ + + + + + + + + + + + + + + +
+Copyright © 2003 Netscape Communications Corp. All rights reserved.
+
+Last Updated July 30, 2003
+
|
+||
|
+ + + + + + + + + + + + + + + + + |
+
++ + + + +
++ + + +Chapter 5 + + + + + +Preparing to Customize the Mozilla Browser +
+ +The CCK tool presents three screens that allow you to customize different aspects of the Mozilla browser. This chapter describes the information and files you need to prepare for these three screens. +
++ +This chapter contains these sections: +
++ +Creating a Custom Animated Logo
+
Determining a Help URL and Menu Item
Determining the Name of the Program Folder in the Windows Start Menu
Preparing a Customized Read-me File
Creating Your Own Sidebar Tab
Specifying the Default Home Page
Preparing Your Customized Bookmarks and Personal Toolbar
Determining Text for the Browser Window's Title Bar
Checklists for Customizing the Browser ++ + +Creating a Custom Animated Logo +
+ + ++ +You can replace the standard Mozilla animated logo that appears in the browser and mail windows with an animated logo for your own company, such as this one for MyISP:
++ +
++ +If you wish, you can also change the URL for the animated logo button to the URL for your home page, so that when users click the animated logo, they go to your home page instead of
+www.mozilla.org. ++ +The animated logo consists of a composite
+.GIFfile that contains two or more individual.GIFimages, or frames, laid end-to-end. When the individual frames in the composite.GIFfile are displayed in rapid succession, one after the other, the logo graphic takes on the appearance of motion. ++ +Here is a series of separate
+.GIFfiles that can be used to construct an animated.GIFfile:+ +
++ +To create your own animated logo, you'll need these tools: +
++ +
+- +A graphics editing program or 3D animation program to create the individual
.GIFfiles, or frames. + ++
+ +- +A
.GIFfile animation program that assembles individual .GIF files into one continuous animated.GIFfile. + ++
++ +You'll need to create the following: +
++ +
+- +A static
.GIFfile (32 by 32 pixels) for the at-rest logo. + ++
+ +- +An animated
.GIFfile (32 by 32 pixels) for the animated logo. + ++
++ +The browser uses the static
+.GIFfile whenever the animated logo is at rest (not animating). When both files are ready, put them in theWorkspace\AnimLogodirectory for your configuration. ++ +The sections that follow outline the steps involved in creating your static and animated
+.GIFfiles. ++ + +Step 1: Create the Animation Frames +
+ + ++ +You'll need to create the following
+.GIFfiles (frames): ++ +
+- +Up to 40 (32 pixels by 32 pixels)
.GIFfiles for assembling into the animated logo + ++
+ +- +One GIF file (32 pixels by 32 pixels) that will be used as the "still" image when the animation is at rest + +
+
++ +Using a graphics editing program or a 3D animation program, create and save each individual animation frame as a separate
+ +.GIFfile. Keep the animation as simple as possible by using the fewest number of frames that convey the motion you want to achieve. ++ +
+- +Create no more than 40 frames (files) for the animated logo + +
+
+ +- +Save your files in
.GIFformat + ++
+ +- +Use no more than 30 colors in each file; 16 colors are best. + +
+
++ + +Step 2: Assemble Your Frames Using a GIF Animation Program +
+ + ++ +Using your GIF file animation program: +
++ +
+- +Assemble the animation frames in the order in which you want them to appear. + +
+
+ +- +Set the duration that each frame will appear. + +
+
+ +- +Set the animation to loop infinitely. + +
+
+ +- +Preview the animation and make any changes until you're satisfied with the results. + +
+
+ +- +Save the animation as a
.GIFfile. + ++
+ +- +Optimize the animation file. Most
.GIFanimation programs allow you to perform some optimization operations that will reduce the size of your animation file. + ++
++ +Note: The animation will play more slowly on computers with slower processors. +
++ + +Determining a Help URL and Menu Item +
+ + ++ +The CCK Tool allows you to add a Help menu item to the Help menu. The name you specify appears as a new menu item above the Release Notes menu item near the bottom of the browser's Help menu. For example: My ISP Customer Support. +
++ +If you specify a new Help menu item, you must also specify a live URL for the page to which your menu item will take users and provide appropriate content for that page. +
++ + +Determining the Name of the Program Folder in the Windows Start Menu +
+ + ++ +To increase customer awareness of your company name and promote your company's identity to your customers, you can add your company name to the Mozilla 1.4.1 program folder name in the Windows Start menu. +
++ +For example, if you specify MyIsp for use with the Start menu, the program folder name in the Start menu appears as "Mozilla by MyIsp" as shown here:
++ +
++ + +Preparing a Customized Read-me File +
+ + ++ +Mozilla includes a standard read-me file, which you might want to customize if you want to provide additional information to your customers. +
++ +Under the terms of the Browser Customization Guidelines, you can edit the existing read-me file or replace it with one of your own, but you must not rename it. +
++ +To edit the read-me file: +
++ +
+- +Locate the standard Mozilla Read Me (
readme.txt) file: + ++
++
+ +- +where installation_directory is the directory where you installed the CCK tool. +
- +Copy the
readme.txtfile to your own Workspace directory + ++
++
+- +where my_config is the name of the configuration you are customizing. +
+ +Using a standard text editor such as WordPad, edit
+readme.txtor replace its contents with your own information. When the file is ready, put it at the top level of theWorkspacedirectory for your configuration (for easy access when you run the CCK tool). ++ + +Creating Your Own Sidebar Tab +
+ + ++ +Sidebar tabs provide a place within the Mozilla 1.4.1 browser for users to keep connected to what is most important to them. Tabs are a great place for favorite information, such as stock quotes, local weather, news headlines, sports headlines, local events, or horoscopes. Users can choose from a wide variety of tabs in the Sidebar Directory. +
++ +Mozilla 1.4.1 comes with several sidebar tabs already set up. However, you can customize the browser by adding, removing, and rearranging tabs for your users. By creating a sidebar tab, you give your content constant presence within the user's client software. This means that users always have access to your service or content even when they are on another web site or using email. Links in your tab can lead back to your web site, driving increased traffic; and you can reduce service calls by making technical information easily accessible through your sidebar tab. +
++ +The sidebar can appear on the left side of browser and mail windows of Mozilla 1.4.1. Here's an example of a custom sidebar tab for MyISP:
++ +
++ +To create a sidebar tab, see the instructions posted at +
+
+
+ + +http://home.netscape.com/sidebar + +++ +To add or rearrange the tabs that appear, see the following sections. After you have created your own sidebar tab and made other modifications to the sidebar tabs displayed, you should store the file
+ + + +panels.rdfin yourWorkspace/Sidebardirectory for easy access when you run the CCK tool. ++ +In addition to providing your own sidebar tab, you can select from a wide range of existing sidebar tabs to customize the default tabs available when your customers open a new Mozilla profile for the first time. +
++ +For a continuously updated directory of available sidebar tabs, see +
+
+
+ + +http://channel.netscape.com/sidebar/sbd/index.tmpl + +++ +For additional information about developing sidebar tabs, see +
++ +It possible to add a sidebar tab simply by clicking a link. You can also control which sidebar tabs appear from within the Sidebar frame itself: +
++ +
+- +Start the Mozilla browser. + +
+
+ +- +Click Tabs at the top of Sidebar, then choose Customize Sidebar. + +
+
+ +- +Select one or more tabs from the list on the left. You can open and close folders by double-clicking their names. + +
+
+ +- +Click Add. + +
+
+ +- +Click OK to finish. + +
+
++ + +Rearranging Sidebar Tabs +
+ + ++ +To change the position of one of the Sidebar tabs displayed by the browser, follow these steps: +
++ +
+ +- +In the browser, click Tabs at the top of Sidebar, then choose Customize Sidebar. + +
+
+ +- +Select a tab from the list on the right. + +
+
+ +- +Click Up or Down to change the tab's placement. + +
+
+ +- +Click OK to finish. + +
+
++ +
+- +Change the Sidebar tab that is open by default when you open a new profile with Mozilla 1.4.1 (currently the News tab). + +
+
+ +- +Remove the Search or Today's Tips sidebar tabs from the Sidebar tabs shown by default when you open a new profile with Mozilla 1.4.1. + +
+
+ +- +Remove any of the Sidebar tabs from the list of tabs available to an end user in the default drop-down list of sidebar tabs available when you open a new profile with Mozilla 1.4.1. (It's OK to add additional tabs). + +
+
++ +All the changes you make to Sidebar are stored in the
+panels.rdffile, which is located in the directory for the Mozilla profile you were using when you made the changes. For information on the location of Mozilla profiles on different platforms, see Appendix C "Mozilla Profile Locations by Platform." ++ +When you are finished making your changes, put
+panels.rdfin theWorkspace\Sidebardirectory for your configuration (for easy access when you run the CCK tool). ++ + +Specifying the Default Home Page +
+ + ++ +If you wish to change the home page to a URL of your choice, you can do so by typing the URL in the CCK tool screen entitled "Customize the Browser - Part Three." The URL you specify determines both the first page launched and the page users will see when they click the Home button. +
++ + +Preparing Your Customized Bookmarks and Personal Toolbar +
+ + ++ +You can create a complete set of customized bookmarks (URLs that direct users to web pages) for your users. You can also customize the buttons that appear in the Personal Toolbar. Bookmarks and Personal Toolbar buttons are stored together in the Bookmarks menu. +
++ +You can use Personal Toolbar buttons to call attention to value-added services you provide and to make it easy for users to find information you want them to see:
++ +
++ +Note: For new users who are installing Mozilla for the first time, your customized bookmarks remain visible even if the user subsequently upgrades to a later version. However, users who are upgrading from a previous version of Mozilla or Netscape Communicator to the version you are providing will not get your customized bookmarks because, for upgraders, Mozilla preserves their existing set of bookmarks. Therefore, for upgraders, you may want to create a Sidebar tab that includes some of the links you want to make available to customers. For details, see "Creating Your Own Sidebar Tab." +
++ +To customize Navigator's bookmarks, you'll first create a new user profile that contains the default set of bookmarks that come with Mozilla. You'll then modify the default bookmarks list so that it includes your custom bookmarks. +
++ + +Creating a New User Profile +
+ + ++ +To create a new user profile, follow these steps: +
++ +
+- +Quit Mozilla if it is running. + +
+
+ +- +Open the Start Menu, choose Programs, Mozilla 1.4.1, and then Profile Manager. + +
+
+ +- +Click Create Profile to create a new user profile. + +
+
+ +- +Enter a name for the profile, for example, "bookmarks", and click Next. + +
+
+ +- +Follow the instructions to finish entering profile information. + +
+
+ +- +When you click Finish, Mozilla starts using the new profile. + +
+
++ + +Creating Custom Bookmarks and Personal Toolbar Buttons +
+ + ++ +To create a set of custom bookmarks and Personal Toolbar buttons using your new profile: +
++ +
+- +Choose Manage Bookmarks from the Bookmarks menu. A window similar to this appears:
+ +
+ ++
++
+ +- +
- +Use the Bookmarks window to add, delete, import, and rearrange (drag) bookmarks to produce the set that you want. + +
+
+ +- +To add an item to the Personal Toolbar, either drag and drop a bookmark onto the Personal Toolbar folder, or highlight the Personal Toolbar folder and use the File menu options to add a new bookmark. Bookmarks you create in the Personal Toolbar folder will appear as buttons on the user's Personal Toolbar. + +
+
+ +- +To remove an item, highlight the associated bookmark in the Toolbar Folder and press Delete, or go to the Edit menu and select Delete. + +
+
+ +- +Close the Bookmarks window when you are finished. + +
+
++ +You can also add a bookmark button to the Personal Toolbar for the page currently displayed in your browser by dragging the bookmark icon (located to the left of URL in the Navigation Toolbar) to a desired place on the Personal Toolbar:
++ +
++ +The pointer changes from an arrow into a hand when it is pointing at the bookmark icon +
++ +Mozilla 1.4.1 creates the customized
+bookmarks.htmlfile in the directory for the profile you were using when you set up your customized bookmarks. For information on the location of Mozilla profiles on different platforms, see Appendix C "Mozilla Profile Locations by Platform." ++ +When you are finished making your changes, put
+bookmarks.htmlin theWorkspace\Bkmksdirectory for your configuration (for easy access when you run the CCK tool). ++ + +Determining Text for the Browser Window's Title Bar +
+ + ++ +You can add your company name to the browser window's title bar, so that your company name appears at the top of every browser window. For example, this illustrates the customized browser window's title bar for a company called MyIsp: +
+ ++ +If you decide you want to customize the browser in this way, you simply specify your company name when the CCK tool displays the screen entitled "Customize the Browser - Part Three." +
++ + +Checklists for Customizing the Browser +
+ + ++ + +Customize the Browser - Part One +
+ + ++ +The screen called Customize the Browser - Part One specifies the following: +
++ +
+- +Animated logo: + +
+
++ +
+ +- +Logo button URL + +
++
- +Path to animated GIF file (stored in
+Workspace\AnimLogo) + ++
- +Path to "at rest" GIF file (stored in
Workspace\AnimLogo)
+ ++
- +Help Menu Item: + +
+
+ ++ + +Customize the Browser - Part Two +
+ + ++ +The screen called Customize the Browser - Part Two specifies the following: +
++ +
+- +Text added to "Mozilla by" in the name of the Mozilla program folder in the Windows Start menu + +
+
+ +- +Path to custom read-me file (stored at top level of
Workspace) + ++
+ +- +Path to custom Sidebar tabs (stored in
Workspace\Sidebar) + ++
++ + +Customize the Browser - Part Three +
+ + ++ +The screen called Customize the Browser - Part Three specifies the following: +
+ + +
++ + + + + diff --git a/mozilla/cck/CCKDocs/cd_cck.htm b/mozilla/cck/CCKDocs/cd_cck.htm new file mode 100644 index 00000000000..42c515e0150 --- /dev/null +++ b/mozilla/cck/CCKDocs/cd_cck.htm @@ -0,0 +1,607 @@ + + + + + + + + +
+
+ + + + + + + + + + + + + + + +
+Copyright © 2003 Netscape Communications Corp. All rights reserved.
+
+Last Updated July 30, 2003
+
|
+||
|
+ + + + + + + + + + + + + + + + + |
+
++ + + + +
++ + + +Chapter 8 + + + + + +Preparing to Customize the CD Autorun Screen +
+ +The CCK tool screen called Customize the CD Autorun Screen specifies background image and text customizations for the CD autorun screen, which appears automatically when users insert your customized Mozilla CD into a CD-ROM drive. +
++ +This chapter describes the information and files you need to prepare if you want to customize the CD autorun screen. It includes these sections: +
++ +What Is the CD Autorun Screen?
+
Customizing the CD Autorun Screen's Background Image
Customizing Text for the CD Autorun Screen
Customizing the Installation Document
Checklist for Customize the CD Autorun Screen ++ + +What Is the CD Autorun Screen? +
+ + ++ +If you plan to create Mozilla installers for CD distribution, you can provide a CD autorun screen that automatically appears when the user inserts your customized Mozilla CD into a CD-ROM drive. +
++ +The CD autorun screen makes it easy for your users to install Mozilla or to read installation instructions before they begin the installation process. +
++ + +About the Default CD Autorun Screen +
+ + ++ +The CCK tool provides a default CD autorun screen that's ready to use:
++ +
++ + +Customizing the Standard CD Autorun Screen +
+ + ++ +Customizing the standard CD autorun screen is optional. If you wish, you can use the CCK tool to customize the following items in the standard CD autorun screen: +
++ +
+- +The background image that appears in the CD autorun screen + +
+
+ +- +The text inside and below the screen's title bar + +
+
+ +- +The contents of the installation text file (
install.txt) + ++
++ +Here is an example of a CD autorun screen that was customized by the CCK tool:
++ +
++ +After you create your CD-based installer using the CCK tool, you can make additional manual customizations to the CD autorun screen, such as adding new screens or buttons. For more information, see Chapter 11 "Manually Customizing the CD Autorun Screen" +
++ + +Customizing the CD Autorun Screen's Background Image +
+ + ++ +You can customize the CD autorun screen's background image if you want to add your company logo or add other images that promote your company's identity. +
++ +The standard background image for the CD autorun screen consists of a 640 pixel by 480 pixel bitmap (
+ +.BMP) file, as illustrated here:+ +
++ +The easiest way to customize the background image is to edit the existing background image, called
+install.bmp, as described in the next section. If you prefer, you can substitute your own custom file as described under "Creating Your Own Custom Background Image." ++ + +Editing the Standard Background Image +
+ + ++ +To edit the standard background image: +
++ +
+- +Locate the standard background bitmap file: + +
+
++
+ +installation_directory\CCKTool\Configs\my_config\Workspace\Autorun\ +Shell\bmps\install.bmp + +++ +where installation_directory is the directory where you installed the CCK tool and my_config is the name of the configuration you are customizing. +
++ +
+- +Using a graphics editing program, open the
isntall.bmpfile and make your changes to it. For example, you might want to add your company's logo and name. + ++
++
+ +- +Note: Do not add text or graphics within the black border area at the bottom of the CD autorun screen. This area is reserved for the CD autorun screen's Browse CD, Back, and Exit buttons. +
- +Save your changes, making sure to save the file in
.BMPformat. If you want, you can save the file using another name. + ++
++
+ +- +In the CCK tool, go to the screen titled "Customize the CD Autorun Screen." +
- +Under Background Bitmap, click Choose File and browse to the location of your custom background image to include it. + +
+
++ + +Creating Your Own Custom Background Image +
+ + ++ +To create your own custom background image for the CD autorun screen: +
++ +
+- +Using a graphics editing program, create a bitmap image that's 640 pixels wide and 480 pixels high. + +
+
++
+ +- +Keep the size of the file as small as possible (325 Kbytes or less) by reducing the number of colors in the file, or by removing or flattening the layers (if you created the image in Photoshop). If your file size is too large, it may not appear in the CD autorun screen. +
- +At the bottom of the background image, create a rectangular border at least 40 pixels high and 640 pixels wide. The CD autorun screen will use this area to display the CD control buttons (Browse CD, Back, and Exit). + +
+
+ +- +Save the image as a
.BMP(bitmap) format file here: + ++
+
+
+- +where installation_directory is the directory where you installed the CCK tool and my_config is the name of the configuration you are customizing. +
+ +Your background bitmap image is now ready to specify when you run the CCK tool. +
++ + +Customizing Text for the CD Autorun Screen +
+ + ++ +The CCK tool's CD autorun screen specifies two text strings for the CD Autorun Screen: +
++ +
+- +Title bar text. Text that appears in the CD autorun screen's title bar after "Mozilla by". For example, if you enter "My ISP" the title bar text will read "Mozilla by My ISP". + +
+
+ +- +Text below title bar. Text that appears just below the title bar. For example: "Welcome to the My ISP Installer for Mozilla 1.4.1." + +
+
++ +You should decide on the exact wording of these strings before you run the CCK tool. +
++ + +Customizing the Installation Document +
+ + ++ +The CD autorun screen includes a button that, when clicked, opens a text document that contains instructions for installing Mozilla. You might want to include additional information in this document that you want your users to know before they install. +
++ +For example, you could add information on your products and services, and tell users how they can contact you for more information. If you're planning to include installers for additional programs as part of your Mozilla installer, this document is a great place to tell your users about the additional programs you're providing. +
++ +To edit the installation document: +
++ +
+- +Locate the standard installation document: + +
+
+ +- +Make a copy of this file and save here: + +
+
++
+ +- +Open the
install.txtdocument using a standard text editor, such as WordPad. +
- +Edit the
install.txtdocument and save your changes. + ++
++ +Your background bitmap image is now ready to specify when you run the CCK tool. +
++ + +Checklist for Customize the CD Autorun Screen +
+ + ++ +The Customize the CD autorun screen specifies the following: +
++ +
+ +- +Background bitmap image (stored as
Workspace\Autorun\Shell\bmps\install.bmp) + ++
+ +- +Title bar text + +
+
++ +
+ +- +text that appears after "Mozilla by" in the title bar + +
++
- +text displayed just below the title bar
+ ++
- +Custom installation text file (stored as
Workspace\Autorun\install.txt) + ++
+
++ + + + + diff --git a/mozilla/cck/CCKDocs/cd_man_cck.htm b/mozilla/cck/CCKDocs/cd_man_cck.htm new file mode 100644 index 00000000000..cbeeac8e42a --- /dev/null +++ b/mozilla/cck/CCKDocs/cd_man_cck.htm @@ -0,0 +1,1899 @@ + + + + + + + + +
+
+ + + + + + + + + + + + + + + +
+Copyright © 2003 Netscape Communications Corp. All rights reserved.
+
+Last Updated October 05, 2001
+
|
+||
|
+ + + + + + + + + + + + + + + + + |
+
++ + + + +
++ + + +Chapter 11 + + + + + +Manually Customizing the CD Autorun Screen +
+ +The CD autorun screen automatically appears when a user inserts a customized Mozilla CD into a CD-ROM drive. The standard CD autorun screen lets your users easily install Mozilla or read installation instructions before they begin installation. You can customize some aspects of this screen, such as the title bar text and background, using the CCK tool. +
++ +If you're planning to distribute a Mozilla installer on a CD, you might want to make more customizations to the standard CD autorun screen than the CCK tool can implement. This chapter describes the manual customizations to the CD autorun screen that you can make, if you wish, to the installation files generated by the CCK tool. +
++ +This chapter contains these sections: +
++ +Why Manually Customize the Standard CD Autorun Screen?
+
Run The CCK Tool First
About the CD Autorun Files
Tools for Customizing the Standard Autorun Screen
Creating a CD Staging Area on Your Hard Disk
Understanding the rshell.ini File
Editing the rshell.ini File
Verifying Your CD Autorun Screen Manual Customizations ++ + +Why Manually Customize the Standard CD Autorun Screen? +
+ + ++ +Chapter 8 "Preparing to Customize the CD Autorun Screen" describes the following customizations that you can make to the standard CD autorun screen using the CCK tool: +
++ +
+- +Customize the CD autorun screen's background bitmap image. + +
+
+ +- +Provide your own title bar text and text below the title bar. + +
+
+ +- +Customize the contents of the installation guide text file. + +
+
++ +You can manually customize the standard CD autorun screen if you want to: +
++ +
+- +Create additional screens that inform users about your products, services, and promotions. + +
+
+ +- +Include additional files or software on the CD. You can add new screens and buttons to the CD autorun screen that give users easy access to the directories on the CD that contain these files, so that users don't have to browse through the directories on the CD to find them. You can also include a button in the CD autorun screen that opens a
readme.txtfile, so users have easy access to information about these additional files. (For information about adding up to two additional installers with the CCK tool, see Chapter 9 "Preparing to Create the Installer." + ++
+ +- +Installers for additional applications on the CD. You can add buttons and text to the standard CD autorun screen that inform users about these applications and make them convenient to install. + +
+
+
+ + ++ +Before manually customizing the standard CD autorun screen, use the CCK tool to create a Mozilla installer that includes the CD autorun screen. Make sure you select the checkbox labeled "Include CD autorun screen" on the Gathering Information screen. Checking this box causes CCK to include the files associated with the CD autorun screen when it creates your customized Mozilla installer. After the CCK tool builds the installer, verify that the CD autorun customizations are correct. +
++ + +About the CD Autorun Files +
+ + ++ +The CD autorun screen is a standard Windows executable program that automatically launches when users insert the CD in a CD-ROM drive. +
++ +When you create your customized Mozilla installer, the CCK tool places the CD Autorun files in this location: +
++
+ +installation_directory\CCKTool\Configs\my_config\Output + +++ +When you are finished editing the CD autorun screen files, you use the contents of the
+Outputdirectory to create your CD layout. ++ +These files and directories are associated with the CD autorun screen: +
++ +
+- +The
Nsetup32.exeprogram (the Autorun program) and thershell.inifile are both located in the directoryOutput\Shell\Nsetup32\. Thershell.inifile contains all of the custom settings and flags that control the appearance and function of the CD autorun screen. + ++
+ +- +
setup.exe,launch.ini, andautorun.infare located in theOutputdirectory, which is the root of the CD layout. They control the automatic launch of the Autorun program and the CD autorun screen. Thelaunch.inifile points to the location of theNsetup32.exeautorun program and its associated file,rshell.ini. If the Autorun screen doesn't automatically launch, users can double-click the setup.exe file. + ++
++ +In addition to controlling the appearance of the CD autorun screen, the
+rshell.inifile also links any number of CD autorun screens together using buttons. The buttons can also point to any installers or files included on your CD that you want users to be able to access. ++ +For more information about preparing your CD layout, see Chapter 14 "Distributing Your Installers." +
++ + +Tools for Customizing the Standard Autorun Screen +
+ + ++ +To customize the standard autorun screen or add new screens, you'll need: +
++ +
+- +Aa standard text editor for editing the
rshell.inifile. + ++
+ +- +A graphics editing program, for creating any custom bitmap images that you want to include as background or button images in the Autorun screens. + +
+
++ +You can include one or more directories inside the shell directory to store the custom bitmap images used by the autorun screens. Depending on the CD layout you want to create, you can also include directories for additional items such as applications that you want users to be able to install by clicking buttons in the CD autorun screen. +
++ + +Creating a CD Staging Area on Your Hard Disk +
+ + ++ +Before you start editing the
+rshell.inifile, you'll need to determine the directory structure on the CD so that you know how to specify the pathnames of files that you want to be accessible through the Autorun screens. You do this by creating a staging area on your hard disk that exactly represents the final CD layout you intend to use. ++ +To create a CD staging area: +
++ +
+- +Create a directory called Staging on your hard disk. + +
+
+ +- +Locate the
Outputdirectory you created using the CCK tool. + ++
+ +- +Copy the contents of the Output directory into the Staging directory. + +
+
+ +- +Inside the
Stagingdirectory, create a directory for each additional component that you want to include on the CD. + ++
++ +Inside the
+Staging\Shelldirectory, you'll find a directory calledbmpsin which you'll store the custom background bitmap images for any new CD autorun screens you create. ++ + +Understanding the rshell.ini File +
+ + ++ +Note: The
+rshell.inifile does not support the usage of double-byte character sets such as those used in the Chinese, Japanese, and Korean languages. ++ +To understand the structure of the
+rshell.inifile, use a standard text editor such as NotePad to openShell\Nsetup32\rshell.ini, and examine the descriptions contained in the file. ++ +The
+rshell.inifile consists of two sections: ++ +
+- +The [General] section is where you specify the attributes of the control buttons (Browse CD, Back, and Exit) that appear at the bottom of the Autorun screens. + +
+
+ +- +The [Dialog] sections specify the attributes and behavior of each Autorun screen. Each [Dialog] section defines one Autorun screen, and you name the [Dialog] sections sequentially as [Dialog1], [Dialog2], [Dialog3], and so on, one for each Autorun screen. + +
+
++ + +General Settings in the rshell.ini File +
+ + ++ +This section describes the general settings in the
+rshell.inifile that apply to all dialogs. ++ + +Text for Browse, Back, and Exit Buttons +
++
+ +browse_button_text=text + +++
+ +back_button_text=text + +++
+ +exit_button_text=text + +++ +Specify the text displayed for the Browse, Back and Exit buttons. The Browse and Exit buttons appear on all dialogs. The Back button only appears if the
+rshell.inifile specifies more than one dialog. ++ +Use an
+ +&(ampersand) in front of the character you want to assign as the keyboard shortcut for this button. For example,browse_button_text=Browse &CDsets C as the keyboard shortcut for this button. ++
+ +browse_button_text=Browse &CD + +++
+ +back_button_text=Back + +++
+ +exit_ button_text=Exit + +++ + +Positions of Browse, Back, and Exit Buttons +
++
+ +browse_button_pos= x1,y1,x2,y2 + +++
+ +back_button_pos= x1,y1,x2,y2 + +++
+ +exit_button_pos= x1,y1,x2,y2 + +++ +Specifies the position of the Browse, Back, and Exit buttons, relative to the top left corner (0,0) of the dialog. If not specified, button position is based on dialog size. +
+ ++ +x1,y1: The upper left coordinates of the button, in pixels, relative to the top left corner of the dialog. +
++ +x2,y2: The lower right coordinates of the button, in pixels, relative to the top left corner of the dialog. These coordinates are ignored if button bitmap files are specified using the
+browse_button_bitmaps,back_button_bitmaps, orexit_button_bitmapssetting. ++ + +Bitmaps for the Browse, Back, and Exit Buttons +
++
+ +browse_button_bitmaps=up.bmp,dn.bmp,sel.bmp,dis.bmp + +++
+ +back_button_bitmaps=up.bmp,dn.bmp,sel.bmp,dis.bmp + +++
+ +exit_button_bitmaps=up.bmp,dn.bmp,sel.bmp,dis.bmp + +++ +Specifies the button bitmaps used for the Browse, Back, and Exit buttons. Four bitmaps specify the four possible states of the button: up, down, selected, disabled. This setting is optional. If you don't specify bitmaps for a button, the dialog uses a standard Windows button with the text specified in
+ +browse_button_text,back_button_text, orexit_button_text. ++ +
+up.bmp: Specifies the bitmap associated with the up (unpressed) button state. ++ +
+dn.bmp: Specifies the bitmap associated with the down (pressed) button state. ++ +
+sel.bmp(optional): Specifies the bitmap associated with the selected (mouse-over) button state. ++ +
+ + + +dis.bmp(optional): Specifies the bitmap associated with the disabled button state. ++ +This section describes the global settings that apply within a dialog. +
+ ++
+ +caption=caption text + +++ +Specifies the text that appears in the dialog's title bar. +
+ ++
+ +dialog_position=x1,y1,x2,y2 + +++ +Specifies the position of the dialog on the monitor screen. If not specified, the dialog is displayed at the center of the monitor screen. If
+ +bk_bitmapis specified, x2,y2 is ignored. ++ +x1,y1: Specifies the coordinates, in pixels, relative to the top left corner (0,0) of the dialog. +
++ +x2,y2: Specifies the coordinates, in pixels, of the lower-right corner of the dialog. +
+ ++
+ +bk_bitmap=background.bmp + +++ +Specifies the background bitmap file used for the dialog. If a background bitmap file is not specified, the dialog uses the system background color for its background color. +
+ ++ +Specifies the vertical gap (y), in pixels, between the buttons in the dialog. +
+ + + ++ +This section describes the settings used for the title text in a dialog. You use these settings to include a line or paragraph of text that can appear anywhere within the dialog. +
+ ++
+ +dialog_title_text=text + +++ +Specifies the title text for the dialog. +
+ ++
+ +dialog_title_pos=x1,y1,x2,y2 + +++ +Specifies the position in pixels, relative to the top left corner of the dialog, of the title text. +
+ ++ +x1,y1: Specifies the position of the top left corner of the text. +
++ +x2,y2: Specifies the position of the bottom right corner of the text. +
++ + +Dialog Title Text Color +
++
+ +dialog_title_text_color=red,green,blue + +++
+ +dialog_title_shadow_color=red,green,blue + +++
+ +dialog_title_shadow_depth=red,green,blue + +++ +Specifies the text color, shadow color, and shadow depth of the dialog title text. You specify a number between 0 (black) and 255 (white) for each of the red, green, and blue values to get the overall pixel color. +
++ +Table 1 lists commonly-used colors from the standard Windows palette.
++ + +Table 11-1 Windows palette colors +
+
++
+ + + + ++ ++ + ++ + + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ ++ ++ + ++ + ++ ++ + ++
+ +dialog_title_text_font=font,size + +++ +Specifies the font and font size used for the dialog's title text. It's best to use a standard font that you know will be available on end users' machines. If not specified, the system font and font size are used. +
++ + +Dialog Title Text Style +
++
+ +dialog_title_font_bold=TRUE/FALSE + +++
+ +dialog_title_font_underline=TRUE/FALSE + +++
+ +dialog_title_font_italic=TRUE/FALSE + +++ +If set to
+TRUE, specifies the font style (bold, italic, underline) used for the dialog's title text. If not specified or if set toFALSE, the style is not applied. ++ + +Global Button Text Settings +
+ + ++ +This section describes the text settings used for all button text in a dialog. +
+ ++ +
+text_color_default=red,green,blue++ +
+text_color_highlight=red,green,blue++ +Specifies the default text color and the mouse-over (highlight) text color of all button text in a dialog. You specify a number between 0 (black) and 255 (white) for each of the red, green, and blue values to get the overall pixel color. The text automatically changes to the mouse-over (highlight) text color when you position the mouse over a button in the dialog. +
++ +Table 11-1 lists commonly used colors from the standard Windows palette. +
++ + +Button Title and Body Text +
++
+ +button_title_text_font=font,size + +++
+ +body_text_font=font,size + +++ +Specifies the font and size used for the dialog's button title text and button body text. It's best to use a standard font that you know will be available on end users' machines. If not specified, the system font and font size are used. +
+ ++
+ +button_title_font_bold=TRUE/FALSE + +++
+ +button_title_font_italic=TRUE/FALSE + +++
+ +button_title_font_underline=TRUE/FALSE + +++ +If set to
+ +TRUE, specifies the font style (bold, italic, underline) used for the dialog's button title text. If not specified or if set toFALSE, the style is not applied. ++
+ +body_text_font_bold=TRUE/FALSE + +++
+ +body_text_font_italic=TRUE/FALSE + +++
+ +body_text_font_underline=TRUE/FALSE + +++ +Specifies the font style (bold, italic, underline) used for the dialog's button body text. If not specified or set to
+FALSE, the style is not applied. ++ + +Column Settings Within a Dialog +
+ + ++ +This section describes the settings used for columns within a dialog. Each dialog can have one or more columns. The settings for the first (left-most) column all begin with col1; the settings for the second column all begin with col2, etc. If you only want one column of buttons in a dialog, delete all of the col2 and greater settings, or you can leave them blank. +
++ + +Position of First Button in Column One +
++
+ +col1_button_pos=x,y + +++ +Specifies the position of the first button in column 1 of a dialog. You specify the x,y coordinates of the upper-left corner of the button, relative to the upper-left corner of the dialog (0,0). If you want, you can specify an offset position for an individual button using the
+button1_offsetsetting described later in this chapter. ++ + +Position of a Button's Descriptive Text +
++
+ +col1_text_offset=offset + +++ +You can use either of these settings to specify the position of the button's descriptive text. Use
+col1_text_offsetif you want to specify the text's position by defining an offset between the button and the button text. Usecol1_text_posxinstead if you want to specify the absolute x position of the button's descriptive text. ++ +If unspecified, the default is
+ +col1_text_offset=10. If both settings are specified,col1_text_offsetis ignored and the absolute x position as specified incol1_text_posxis used. ++ +Specifies the distance x, relative to the left edge of the dialog box, at which the button descriptive text wordwraps to the next line. If this setting is not specified, the text wordwraps when it is 10 pixels to the left of the right edge of the dialog. +
++ + +Button Settings Within a Dialog +
+ + ++ +This section describes the settings used for buttons within a dialog. Each dialog can have one or more buttons. The settings for the first button all begin with button1, the settings for the second button all begin with button2, and so on. If you only want one button in a dialog, delete all of the button2 and greater settings, or leave them blank. +
+ ++ +
+button1_bitmaps= up.bmp,dn.bmp,sel.bmp,dis.bmp++ +Specifies the button bitmaps used for button1. Four bitmaps specify the four possible states of the button: up, down, selected, disabled. This setting is optional. If you don't specify bitmaps for a button, the dialog uses a standard Windows button with the text specified in
+ +button1_text_title. ++ +
+up.bmp: Specifies the bitmap associated with the up (unpressed) button state. ++ +
+dn.bmp: Specifies the bitmap associated with the down (pressed) button state. ++ +
+sel.bmp(optional): Specifies the bitmap associated with the selected (mouse-over) button state. ++ +
+ +dis.bmp(optional): Specifies the bitmap associated with the disabled button state. ++
+ +button1_cmdline=action,target + +++ +Specifies the action you want to assign to the button. Clicking a button can cause one of seven possible actions, depending on the value you specify for the action argument. The possible button actions and arguments are: +
++ +
+ +- +Launch a program (
action=exe) + ++
++
+ +- +Example:
button1_cmdline=exe,..\..\Mozilla\setup.exe+
- +Go to a different dialog screen (
action=window) + ++
++
+ +- +Example:
button1_cmdline=window,dialog2+
- +Open a file (
action=open) + ++
++
+ +- +The file opens with whatever program the operating system has associated with the file's type. If a file type association doesn't exist, Windows asks the user to choose a program. +
- +Example:
button1_cmdline=open,..\..\install.txt+
- +Print a file (
action=print) + ++
++
+ +- +The file is printed with whatever program the operating system has associated with the file's type. If a file type association doesn't exist, Windows asks the user to choose a program. +
- +Note: You cannot print HTML files through Windows. +
- +Example:
button1_cmdline=print,..\..\install.txt+
- +Explore a directory on the CD (
action=explore) + ++
++
+ +- +Opens the specified directory on the CD. The directory path must be specified as an absolute path from the root of the CD. +
- +Example:
button1_cmdline=explore,extras\clipartopens theextras\clipartdirectory, which is at the root level of the CD. +
- +Open a file in the Mozilla Browser (
action=mozilla) + ++
++
+ +- +Opens the specified file using the currently-installed version of the Mozilla Browser. The file type can be
.html,.gif,.jpeg, or any other file type that the browser can open, such as
- +Example:
button1_cmdline=mozilla,myfile.html+
- +Create a shortcut on the desktop (
action=desktop) + ++
++
+- +When button1 is clicked, a shortcut is created on the desktop, using the specified shortcut name and icon file, that opens the specified file or directory on the CD. File or directory paths must be specified as absolute paths from the root of the CD. +
- +Example:
button1_cmdline=desktop,readme.txt,Read Me,\shell\icons\readme.ico+
- +Button Text +
- +Specifies the button title text and body text for button1. +
+ +Specifies the button's horizontal (x) and vertical (y) offset, in pixels, from the location specified in the
+col1_button_possetting. If there is more than one button in column 1, and you only specify an offset for button1, the other buttons in the same column will use the same vertical (y) offset. You can change the offsets for the other buttons by specifying individual button offsets for each of them. ++ + +Editing the rshell.ini File +
+ + ++ +To edit the rshell.ini file: +
++ +
+ + + +- +Locate the
Staging\Shell\nsetup32\rshell.inifile and open it using a standard text editor. Familiarize yourself with the settings in thershell.inifile. + ++
+ +- +Decide how many dialog screens you want to use. If you need more dialog screens than are defined in the
rshell.inifile, copy an entire[Dialogx] section (where x is a unique number associated with each dialog) and paste it as needed into the file. Each dialog screen must have a unique number. If you need fewer than are provided by default, remove entire[Dialogx] sections as necessary. + ++
+ +- +Design the layout, background images, buttons, and text for each dialog screen. Make the necessary customizations in the settings in the rshell.ini file. + +
+
++
+ +- +Note: Rather than entering the text for a screen in the
rshell.inifile, you may prefer to create your text as part of the background image using an image editing program such as Adobe Photoshop. Using an image editing program gives you more control over the appearance of the text, including fonts and colors. +
- +Assign an action to each button in each dialog screen. + +
+
+ +- +Save your changes to the
rshell.inifile in place; do not move the file. + ++
++ +The supplied
+rshell.inifile includes a second dialog, Dialog2, that is not visible by default. To enable it, locate the button3 settings that are commented out with semicolons (located within the section in thershell.inifile called "Buttons 2 - 6 for Dialog 1"). Remove the semicolons in front of all the button3 settings, save your changes, and then launch the Autorun screen by double-clicking the fileShell\nsetup32\Nsetup32.exefile. Click the third button in the first screen (labeled Bonus Applications and Plug-ins) and you'll be able to see the second dialog. ++ +To add a new Autorun screen: +
++ +
+- +Locate the file
Staging\Shell\nsetup32\rshell.inifile and open it using a text editor. + ++
+ +- +Copy an entire
[Dialogx]section and paste it into thershell.inifile at the location where you want the new screen to appear. + ++
+ +- +Increment the value of x in the
[Dialogx] identifier, so that the[Dialogx] section has a unique number. Each[Dialogx] section must have a unique number associated with it, such as[Dialogx],[Dialogx],[Dialogx]. + ++
+ +- +Make the necessary customizations to each
[Dialogx] section. + ++
+ +- +Save your changes to the
rshell.inifile in place; do not move the file. + ++
++ + +Adding A Background Image to a Dialog Screen +
+ + ++ +If you don't specify a background image for a new screen, the new screen uses the system background color. To add a background image to a new screen, follow these steps: +
++ +
+- +Using a graphic editing program, create a background bitmap that's 640 x 480 pixels, and save it as a
.BMPformat file in theshell\bmps\directory. + ++
++
+- +Keep the following in mind: +
+ +
+ +- +Keep your bitmap file sizes as small as possible by reducing the number of colors the images use or by removing (flattening) the layers if you created the images in Adobe Photoshop. If your images are too large, you may not be able to see them in the Autorun screen. If you cannot see a background image when you test the Autorun screen, open the image in a paint program and try reducing the number of colors to reduce the image's file size. + +
++
- +To prevent palette-swapping when switching between Autorun screens, be sure to use a 256-color palette in each background image you create. + +
++
- +Be sure to leave room at the bottom of the background bitmap (about 40 pixels in height, preferably black) for placement of the control buttons (Browse CD, Back, and Exit) specified in the rshell.ini file. + +
+
+
+- +For example, here is an illustration of the background bitmap image used to create the standard Autorun screen. Note that a black area 40 pixels high was created at the bottom of the image, to allow placement of the control buttons.
+ +
+
- +Open the rshell.ini file using a text editor. + +
+
+ +- +Locate the dialog section that you want to customize. + +
+
+ +- +To the right of the
bk_bitmap= setting, enter the path to the bitmap file, relative to the location of the shell directory. For example: + ++
+ +- +Save your changes to the
rshell.inifile in place; do not move the file. + ++
++ + +Customizing a Screen's Title Bar Text +
+ + ++ +The title bar appears at the top of every autorun dialog screen. You may want to include your company's name in the title bar or provide other identifying information. For example, this screen shows customized text in a CD autorun screen's title bar:
++ +
++ +To customize a screen's title bar: +
++ +
+- +Open the
rshell.ini fileusing a text editor. + ++
+ +- +Locate the
[Dialogx]section that you want to customize. + ++
+ +- +To the right of the
caption= setting,enter the text that you want to appear in the screen's title bar. + ++
+ + +- +Save your changes to the
rshell.inifile in place; do not move the file. + ++
++ + +Adding a New Button to a Screen +
+ + ++ +You can add a button to an autorun screen that performs any of these functions: +
++ +
+- +Launch an executable (
.exe) program. + ++
++
+ +- +For example, if you want to include an installer for another application on the CD, you can add a button that users can click to launch the installer. +
- +Go to another screen + +
+
++
+ +- +For example, if you're creating multiple CD autorun screens, you can add a button that users can click to go to a particular screen. (This is in addition to the standard Browse, Back, and Exit buttons that appear on each autorun screen.) +
- +Open a file + +
+
++
+ +- +For example, you can add a button that opens a
readme.txtfile so that users can read installation instructions for another application you're providing on the CD. +
- +Print a text file + +
+
++
+ +- +For example, you can add a button that prints the installation instructions. +
- +Explore a directory + +
+
++
+ +- +For example, if you're including a directory of utilities on the CD, you can add a button that opens that directory so that user can view its contents. +
- +Open a file in the Mozilla Browser + +
+
++
+ +- +For example, if you've provided an HTML or GIF format file on the CD that you want users to view in Navigator, you can add a button that opens the file using an already-installed version of Navigator. +
- +Create a shortcut on the user's desktop + +
+
++
+- +For example, if there's a directory on the CD that you want users to have easy access to, you can create a desktop shortcut for that directory. +
+ +To add a new button to an Autorun dialog screen: +
++ +
+- +Open the
rshell.inifile using a text editor. + ++
+ +- +Locate the dialog section where you want to add a new button. + +
+
+ +- +Within the dialog section, locate the section where the buttons for the dialog are defined. Each button group begins with + +
+
++
+ +- +
button1_bitmaps=+
- +Decide how many buttons you want to appear in the dialog. + +
+
+ +- +If you need more buttons than are defined by default in the
rshell.inifile, copy and paste new button groups and increment the button number for each new group you add. + ++
+ +- +To remove buttons, delete the button groups that are above the number you need, or simply leave their settings blank. + +
+
+ +- +Assign an action to each button using the
buttonx_cmdline=setting. You can define any one of seven different button actions. See the description of thebuttonx_cmdline=setting earlier in this chapter, or by referring to the comments in the rshell.ini file. + ++
++
+ +- +For example, to have button1 go to the dialog2 screen, you would enter: +
- +For example, to have button1 launch a program named Setup.exe, you would enter: +
- +When you have finished defining buttons and button actions, save your changes to the
rshell.inifile. + ++
++ + +Verifying Your CD Autorun Screen Manual Customizations +
+ + ++ +After you finish editing the
+ + + +rshell.inifile, you should view your custom Autorun screens so you can verify your customizations. Follow these steps: +
++ + + + + diff --git a/mozilla/cck/CCKDocs/config_cck.htm b/mozilla/cck/CCKDocs/config_cck.htm new file mode 100644 index 00000000000..68d774f2c52 --- /dev/null +++ b/mozilla/cck/CCKDocs/config_cck.htm @@ -0,0 +1,1001 @@ + + + + + + + + +
+
+ + + + + + + + + + + + + + + +
+Copyright © 2003 Netscape Communications Corp. All rights reserved.
+
+Last Updated October 05, 2001
+
|
+||
|
+ + + + + + + + + + + + + + + + + |
+
++ + + + +
++ + + +Chapter 3 + + + + + +Using the Configuration Workspace for Customized Files +
+ +As you saw in Chapter 2 "Customizing Mozilla in Ten Minutes," the first screen presented by the CCK tool allows you to select a configuration (or create a new one). Each configuration available to the CCK tool has a corresponding directory where the installer for that configuration resides. +
++ +The configuration directory also includes a Workspace directory. If you need to do create an animated logo or customize bookmarks, the default My Sidebar tabs, the read-me file, and other aspects of Mozilla 1.4.1. that require you to prepare files before running the CCK tool, you can use the Workspace to store your customized files while you work on them. +
++ +This chapter describes the contents of the configuration directory, the files you can customize, and where to store them in the Workspace directory. The chapters that follow summarize how to prepare the information and files relevant to each of the remaining screens presented by the CCK tool. +
++ +This chapter contains these sections: +
++ +Creating a New Installer Configuration
+
The Configuration Directory
Customized Files Checklist
Platform and Configuration Information ++ + +Creating a New Installer Configuration +
+ + ++ +The first screen of the CCK tool includes a drop-down list (near the lower-left corner) that allows you to select a configuration. You can also use this screen to create a new configuration or create a copy of an existing configuration. +
++ +Each configuration name in the drop-down list corresponds to a configuration directory of the same name (described in detail in the section that follows). A configuration directory stores both customized files that you supply for use by the CCK tool and the customized Mozilla 1.4.1 installation files created by the CCK tool. +
++ +The CCK tool applies the customizations you specify to the configuration selected in the first screen. If you are customizing features that require you to prepare custom files in advance, you should prepare and verify those files before you run the tool. +
++ +The rest of this chapter describes the layout of the configuration directory and summarizes the files you must prepare for various customizations. The chapters that follow describe how to prepare the customized files for the customizations you can specify with the CCK tool. +
++ + +The Configuration Directory +
+ + ++ +Each configuration name listed in the drop-down list on the first screen of the CCK tool corresponds to a directory name in this location: +
++ +After you run the CCK tool for a given configuration, the corresponding configuration directory contains the following subdirectories and files (assuming the configuration includes a CD autorun screen as well as a network installer): +
++ +
+- +
Outputcontains all customized installation files: + ++
++ +
+ +- +
+Core+ ++
- +
+Shell+ ++
- +
+autorun.inf+ ++
- +
+install.txt+ ++
- +
+launch.ini+ ++
- +
setup.exe
+ ++
- +
Workspaceincludes the following subdirectories for storing your customized files: + ++
++ +
+- +
+AnimLogostores the .GIF files associated with the animated logo button. See Customizing the Mozilla Browser for the instructions to create these files. + ++
- +
+Autorunstores a custom background image for the CD autorun screen. See Customizing the CD Autorun Screen for the instructions to create the custom files. + ++
- +
+Bkmarksstores a custom bookmarks file for the Navigator browser. See Customizing the Mozilla Browser for the instructions to create this file. + ++
- +
+CustInststores additional installers (in the form of self-extracting executable files) that will run after the main installation completes. See Creating Mozilla Installers for more information about providing additional installers. + ++
- +
Sidebarstores a custompanels.rdffile, which contains the sidebar information used by the browser. See Customizing the Mozilla Browser for instructions on modifying the default panels.rdf file. + ++
+ +In the default and sample MyISP configurations,
+license.txtandreadme.txt(the Mozilla license and read-me files) are located in theOutputdirectory. In all other configurations, these two files are located one level higher (in the my_config directory). ++ + +Customized Files Checklist +
+ + ++ +Table 3-1 lists the customizations that require customized files and where to find information about preparing those files. +
++ + +Table 3-1 Mozilla 1.4.1 customized file checklist + +
+ +
++
+ + + ++ ++ + ++ + ++ + ++ + + ++ ++ ++ ++ +Animated and at-rest GIF files (32 x 32) for the animated logo +
+ ++ + ++ +Chapter 5 "Preparing to Customize the Mozilla Browser"page 67 +
+ ++ ++ ++ ++ + ++ +Chapter 5 "Preparing to Customize the Mozilla Browser"page 67 +
+ ++ ++ +Custom background graphic for CD autorun screen (for CD-based installers) +
+ ++ +640 x 480 bitmap file containing your custom background image +
+ ++ + ++ +Chapter 8 "Preparing to Customize the CD Autorun Screen" +
+ ++ ++ ++ ++ + ++ +Chapter 8 "Preparing to Customize the CD Autorun Screen" +
+ ++ ++ ++ +The
setup.exefor each additional installer (up to two) ++ ++ + ++ ++ ++ ++ ++ + ++ +Chapter 5 "Preparing to Customize the Mozilla Browser"page 67 +
+ + ++ ++ ++ ++ + ++ +Chapter 5 "Preparing to Customize the Mozilla Browser"page 67 +
+ + +Platform and Configuration Information +
+ + ++ +Table 3-2 summarizes the Mozilla 1.4.1 customizations you can make with the CCK tool and the platforms on which they are supported. +
++ + +Table 3-2 Summary of CCK tool customizations + +
+ +
++
+ + + + + ++ ++ + ++ + ++ + ++ + + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ ++ ++ ++ ++ + ++ + ++ ++ ++ ++ + +
++ + + + + diff --git a/mozilla/cck/CCKDocs/cust_ten_cck.htm b/mozilla/cck/CCKDocs/cust_ten_cck.htm new file mode 100644 index 00000000000..4a91700e728 --- /dev/null +++ b/mozilla/cck/CCKDocs/cust_ten_cck.htm @@ -0,0 +1,647 @@ + + + + + + + + +
+
+ + + + + + + + + + + + + + + +
+Copyright © 2003 Netscape Communications Corp. All rights reserved.
+
+Last Updated July 30, 2003
+
|
+||
|
+ + + + + + + + + + + + + + + + + |
+
++ + + + +
++ + + +Chapter 2 + + + + + +Customizing Mozilla in Ten Minutes +
+ +This chapter shows you how to use the CCK tool to implement some of the simplest customizationsthat is, those that don't require you to prepare any files beforehand. +
++ +Other customizations that you can perform with the CCK tool, such as providing your own custom bookmarks or custom animated logo, require that you create customized files before you run the tool. Later chapters describe the preparations required for those customizations. +
++ +This chapter contains these sections: +
++ +What You'll Customize
+
Quick Customization Instructions
Verifying Your Customizations +
+ + ++ +This chapter describers how to create a CD-based Mozilla installer for use on Windows that includes these customizations: +
++ +
+- +Your company name displayed in these locations: + +
+
++ +
+ +- +Browser window's title bar. + +
++
- +CD autorun screen, which is the screen that users see when they insert the Mozilla CD into a CD-ROM drive. + +
++
- +Mozilla program folder name that appears in the Windows Start menu.
+ ++
- +The browser's default home page set to your own home page. The home page is the first page users see when they start Navigator and the page they see when they click the Navigator Home button. + +
+
+ +- +Mail and News server settings. + +
+
+ +- +A Mozilla installer that installs only the components you want users to have. + +
+
++ +If these are the only customizations you need to make, your installer will be ready for packaging and distribution after you finish this chapter. +
++ +Even if you plan to make some of the additional customizations that require preparing files, it's still a good idea to follow the steps described in this chapter as a way of familiarizing yourself with the CCK Tool. Once you have prepared the additional files you need, you can run the tool again to add those customizations to the ones you make in this chapter. +
++ + +Quick Customization Instructions +
+ + ++ +This section guides you through the process of running the CCK tool, which is basically the same whether you are performing the simple customizations described here or those requiring some file preparation as described in the chapters that follow. +
++ +The examples shown in this section are based on the sample configuration provided with the tool for a hypothetical ISP called MyISP. You should, of course, enter the equivalent information for your own company in each screen. +
++ +The steps that follow describe how to create a customized Mozilla installer that implements the simple customizations described in the previous section. +
++ +
+- +Open the Start menu and choose Programs, then Mozilla Client Customization Kit, then N6CCKTool. + +
+
+ +- +Welcome to the Mozilla Client Customization Kit! On the first screen you see when you run the CCK Tool, click New Configuration, enter a name for the directory that the CCK tool will use to store your custom configuration information, and click Create New Configuration. Then click Next to continue.
+ +
+ ++
+ +- +Specify Platform Information. You can choose to generate a Windows or a Linux installer. It's also possible to create a Macintosh installer by manipulating the installation files produced for a Windows installer. + +
+
++
+ +- +For now, leave Windows as the selected platform.
+ +
+
- +Gathering Information. This screen specifies whether you want a CD-ready installer, the FTP address (if any) you plan to use for a network-ready installer, and the company identifier that will appear as part of the user agent string.
+ +
+ ++
++ +
+- +Confirm that the checkbox labeled "Include CD Autorun Screen" is selected. + +
++
- +Enter your company identifier in the field for that purpose near the bottom of the screen
+ ++
+
+ +- +The company identifier you enter will be included as part of the user agent string, which helps identify the browser type each the browser accesses your web site or any other web site. Your identifier in the user agent string allows your company (or others) to track the number of times Internet web sites are accessed by web browsers that you've customized. +
- +The identifier you supply can be up to 10 characters in length. You must supply one. +
- +For example, if you enter "MyISP" in the Company Identifier field, the resulting user agent string would look like this: +
- +When you are ready, click Next to register the customizations you've made on this screen and proceed to the next screen. +
- +Customize the Mozilla Browser - Part One. This screen allows you to customize the animated logo near the upper-right corner of the Navigator window and to add a Help menu item.
+ +
+ ++
++
+ +- +For now, you won't be performing these customizationsbut you can come back and do them later if you wish. Just click Next to proceed to the next screen. +
- +Customize the Mozilla Browser - Part Two. This screen specifies the program folder name that appears under Start Menu/Programs, a custom read-me file, and the files to use for a custom animated logo.
+ +
+ ++
++
+ +- +For now, just enter your company name in the Start Menu section, then click Next. +
- +Customize the Mozilla Browser - Part Three. This screen specifies the default home page, bookmarks file, and title bar text.
+ +
+ ++
++ +
+- +Under Default Home Page, enter the URL for the web page that you want to assign as Navigator's default home page. + +
++
- +Under Browser Window's Title Bar Text, enter your company name.
+ ++
+
+ +- +Click Next to continue. +
- +Customize Mozilla Mail. This screen specifies your mail domain and server information.
+ +
If you choose to provide customized mail settings, fill in every field in the Customize Mozilla Mail screen. You must fill in all fields, otherwise no customized mail server settings will appear in your customized version of Mozilla 1.4.1. + ++
++
+ +- +For short descriptions of the information to enter in each field, click the Help button. For examples of the settings that each field controls, click the corresponding Show Example buttons. Click Next when you are finished. +
- +
- +Customize Mozilla News. This screen specifies your mail domain and server information.
+ +
+ ++
++
+ +- +If you choose to provide customized news settings, fill in every field in the Customize Mozilla News screen. You must fill in all fields, otherwise no customized news server settings will appear in your customized version of Mozilla 1.4.1. +
- +For short descriptions of the information to enter in each field, click the Help button. For examples of the settings that each field controls, click the corresponding Show Example buttons. Click Next when you are finished. +
- +
- +Customize Proxy Configurations. This screen specifies the default proxy configurations that appear under the Advanced category when the user chooses Preferences from the Edit menu.
+ +
+ ++
++
+ +- +For now, you won't specify any proxy configurations. Click Next to continue. +
- +Customize the CD Autorun Screen. This screen specifies the background, title bar text, and installation text file for the CD autorun screen that appears when a user inserts the CD with your custom installer on it.
+ +
Under Title Bar Text, enter your company name as you want it to appear in the screen's title bar and in the area below the title bar of the CD autorun screen. Then click Next to continue. + ++
+ +- +Create the Installer. This screen specifies which Mozilla 1.4.1 components you want to install and up to two additional installers to include with the Mozilla 1.4.1 installer.
+ +
+ ++
++
+ +- +Deselect any components in the list on the left that you don't want to include in your installer. +
- +Before building the installer, click To confirm the settings you have selected, click Show Config Info to confirm all the settings you've made to your configuration. If you see any errors, click the Back button repeatedly to return to the screen where the error occurred. After you've corrected any errors, click the Next button for each screen until you see the Create the Installer screen again. +
- +If you are sure all your settings are correct, click Build Installer to create your customized Mozilla 1.4.1 installer. +
- +When the CCK tool informs you that your installer has been created, click OK. The CCK tool creates your installer files in this location (where installation_directory is the directory where you installed the CCK tool and my_config is the directory name you specified in the first screen): + +
+
++ + +Verifying Your Customizations +
+ + ++ +Once you've created a customized Mozilla installer, you should install your customized software in the same way your users will, so you can verify that all your customizations appear exactly as you intended. Follow these steps: +
++ +
+- +Go to the directory that contains your customized installer and its associated files: + +
+
+ +- +Double-click the file
setup.exe. This causes the CD autorun screen to appearthe same screen your users will see when they insert the CD that contains your customized Mozilla installer. + ++
+ +- +Examine the CD autorun screen to verify that it includes your company name in the title bar and in the area below the title bar. + +
+
+ +- +Click Install Mozilla 1.4.1 to launch the installer. Choose the Custom installation path so you can verify that the components installed by default are the same ones that you selected using the CCK tool. + +
+
+ +- +Choose About Mozilla 1.4.1 from the Help menu and verify your customized user agent string, which should appear near the top of the window. For example: + +
+
+ +- +Verify that the Mozilla program folder name in the Windows Start/Programs menu includes your company name. + +
+
+ +- +Click the Home button in the Navigator browser to verify that it takes you to the URL you specified, and check the browser window title bar to verify that it includes your company name. + +
+
+ +- +Verify that the Mail and News account settings are correct. + +
+
++ +That's all there is to it. If these are the only customizations you want to make, you're ready to begin preparing for distribution: +
++ +
+ + +- +If you want to create a Linux or Macintosh installer, see Chapter 4 "Preparing Platform and Installer Information." + +
+
+ +- +If you want to create a Macintosh installer, you should also see Chapter 13 "Preparing Macintosh Installers and Program Files." + +
+
+ +- +When you are ready to distribute your installers, see Chapter 14 "Distributing Your Installers." + +
+
+
++ + + + + diff --git a/mozilla/cck/CCKDocs/distribute_cck.htm b/mozilla/cck/CCKDocs/distribute_cck.htm new file mode 100644 index 00000000000..5806438d4f5 --- /dev/null +++ b/mozilla/cck/CCKDocs/distribute_cck.htm @@ -0,0 +1,962 @@ + + + + + + + + +
+
+ + + + + + + + + + + + + + + +
+Copyright © 2003 Netscape Communications Corp. All rights reserved.
+
+Last Updated July 30, 2003
+
|
+||
|
+ + + + + + + + + + + + + + + + + |
+
++ + + + +
++ + + +Chapter 14 + + + + + +Distributing Your Installers +
+ +Once you have generated and tested your customized installers, you need to prepare them for distribution. This chapter summarizes some of the major tasks involved. +
++ +This chapter contains these sections: +
++ +Distributing a CD-Based Installer
+
Distributing Network-Downloadable Installers or Binaries ++ + +Distributing a CD-Based Installer +
+ + ++ +The general process for distributing Mozilla installers on CDs works like this: +
++ +
+- +Verify your CD layout. + +
+
+ +- +Create the CD master disc. + +
+
+ +- +Verify and virus check the CD master disc. + +
+
+ +- +Create an archive copy of the CD master disc. + +
+
+ +- +Deliver CD master disc for duplication. + +
+
+ +- +Distribute CDs. + +
+
++ +The sections that follow describe how to verify your CD layout and prepare your files for CD distribution. +
+ ++ + +Verifying Your CD Layout (No Autorun Screen) +
+ + ++ +If you didn't include a CD autorun screen, verify the files for your CD layout as described below. +
+ ++ +Verify your CD layout for Windows as follows: +
++ +
+ +- +Open the directory + +
+
++
+- +Verify that it includes the following files: +
+ +
+ +- +A file called
+Setup.exe, which is the Mozilla installer file. + ++
- +A set of
+.xpifiles, which contain the Mozilla component files in archive format. + ++
- +
autorun.inf, which automatically launches the Mozilla installersetup.exefile when the user inserts the Mozilla CD into a CD-ROM drive.
+ ++
- +Remove the file called
Setup.exe, since it's not needed. Users will double-click thesetup.exeinstaller file to begin installation. + ++
+ +- +Go to "Preparing Your CD-Ready Files for CD Distribution,", later in this chapter. + +
+
++ +For Macintosh, you need to verify the contents of the Mozilla Full Installer folder that you modified as described above under Building Macintosh Installers. It should contain the following files and directories: +
++ +
+- +Mozilla Installer + +
+
+ +- +Mozilla read-me file + +
+
+ +- +License + +
+
+ +- +Installer Modules (folder that includes
config.ini,installer.ini, and all the.xpifiles) + ++
++ +After confirming that these files and directories, go to "Preparing Your CD-Ready Files for CD Distribution." +
+ ++ +After you run the CCK tool to create a Linux installer, decompress the Linux tar file located in this directory: +
++ +The decompressed files should look like this: +
++ +
+- +
xpidirectory + ++
+ +- +
config.ini+ ++
+ +- +
installer.ini+ ++
+ +- +
license.txt+ ++
+ +- +
mozilla-installer+ ++
+ +- +
mozilla-installer-bin+ ++
+ +- +
README+ ++
++ +After confirming that these files and directories, go to "Preparing Your CD-Ready Files for CD Distribution." +
++ + +Assembling Your CD Layout (Autorun Screen) +
+ + ++ +If you included a CD autorun screen for your Windows installer, assemble the files for your CD layout as follows: +
++ +
+- +Open the directory + +
+
++
+- +Verify that the Output directory contains the following: +
+ +
+- +A directory called
+Core, which contains the customized Mozilla files + ++
- +A directory called
+Shell, containing the subdirectories\Bmpsand\Nsetup32, which include the files for the CD autorun screen + ++
- +
+Autorun.inf(launches thesetup.exeat the root of the CD image after the CD is inserted in the drive) + ++
- +
+Launch.ini(configuressetup.exeand detects Windows operating system) + ++
- +
setup.exe (launches nsetup32.exe, which displays the first Autorun screen)
+ ++
+
+ +- +Your CD layout should follow the same general layout as the typical one illustrated here:
+ +
+
- +Verify that the
Shelldirectory contains these files and folders: + ++
++ +
+ +- +A folder called
+\Bmps, which contains all the standard and customized bitmap (.bmp) files used by the CD autorun screens + ++
- +A folder called
\Nsetup32, which contains the following: + ++
+ +
+- +
+Nsetup32.exe, the autorun program + ++
- +
rshell.ini, the file that defines the appearance and behavior of the Autorun screens. See Chapter 11 "Manually Customizing the CD Autorun Screen" for information on how to manually customize this file.
+ ++
- +If you've manually customized the CD autorun screen so that users can install additional plug-ins or applications from the Autorun screens, create a directory called
Xinstallinside the directory + ++
++
+ +- +Buttons you add to your CD autorun screens can be linked to the executable files you include in the
Xinstalldirectory, so that users can install additional software simply by clicking a button. +
- +Put the additional installers into subdirectories inside the directory + +
+
++
+ +- +Important: Make sure that the actual locations of the additional installers match the file pathnames you specified for them in the
rshell.inifile. +
- +If you've manually customized the CD autorun screen to open any other files, such as a
readme.txtfile, include the additional files inside the directory + ++
++
+- +and make sure that their locations match the file pathnames you specified for them in the
rshell.inifile. +
+ + +Preparing Your CD-Ready Files for CD Distribution +
+ + ++ +To prepare your CD-ready files for CD distribution, you need the following: +
++ +
+- +Software to create a data CD, such as Adaptec Easy CD Creator or Adaptec Toast + +
+
+ +- +CD recorder, for creating your master CD + +
+
+ +- +CD-recordable discs, available where you purchased your CD recorder + +
+
+ +- +Bit-compare program such as Microsoft's WinDiff utility + +
+
+ +- +virus checker program + +
+
+ +- +CD duplication service, to make copies of your master CD + +
+
++ +Follow these steps to create a master CD disc: +
++ +
+- +If you didn't include a CD Autorun Screen, verify the files in your CD layout as described in Verifying Your CD Layout (No Autorun Screen). If you included a CD autorun screen, assemble the files for your CD layout as described in Assembling Your CD Layout (Autorun Screen). + +
+
+ +- +Using your CD creation software, create a CD master disc that contains all the files from the directory + +
+
++
+ +- +If you are creating a hybrid CD that includes a Macintosh partition, you also need to specify the location of the Mozilla Full Installer folder that you modified as described in Chapter 13 "Preparing Macintosh Installers and Program Files". +
- +If you are creating a hybrid CD that includes a Linux partition, you also need to specify the location of the Linux installation files that you decompressed from the Linux tar file produced by the CCK tool. +
- +Using a bit-compare utility such as Microsoft WinDiff, verify that the files on the CD exactly match the files in the \Output directory on your hard disk. + +
+
++
+ +- +If the files don't compare exactly, make sure you're comparing the correct set of files on your hard disk with the files on the master CD. The most common reason bit comparisons fail is that the wrong set of files are being compared. +
- +Using a virus checker program, verify that the files on the CD are virus free. + +
+
++
+ +- +Your gold master disc is now ready for duplication. +
- +Create a second gold master disc and keep it in a safe place for archive purposes. + +
+
+ +- +Provide your gold master disc to a CD duplication service. + +
+
++
+ +- +Before the duplication service completes your entire order, be sure to request that the duplication service sends you the first several CDs, so you can verify that the contents of these CDs exactly matches your gold master archive CD. Alternatively, you can request that the duplication service performs this step. +
- +Distribute the CDs to your customers. + +
+
++ +Depending on how you plan to distribute your CDs, you may want to create a printed cover that can be inserted into the CD's plastic jewel case (the plastic case that contains the CD). Your duplication service may offer this service to you. Alternatively, programs such as Adaptec Easy CD Creator include a template for creating printed jewel case inserts. +
++ + +Distributing Network-Downloadable Installers or Binaries +
+ + ++ +To distribute Mozilla 1.4.1 over the network: +
++ +
+- +On your FTP site, create a Mozilla download directory that corresponds to: + +
+
++ +
+ +- +For Windows and Mac OS 9 (stub installers): the location you entered for the FTP directory in the CCK tool.This is the directory you'll use to store the Mozilla installer files. + +
++
- +For Linux (fat installer): the location where you plan to put the Linux tar file produced by the CCK tool. + +
++
- +For Mac OS X (customized binaries): the location where you plan to put the compressed Mac OS X files you modified using your customized Windows installation files.
+ ++
- +If you are preparing a Windows installer, copy the contents of the directory + +
+
++
+ +- +into the download directory on your FTP or HTTP site. +
- +If you are providing a Macintosh installer (Mac OS 9) or binaries (Mac OS X) for network download, you also need to copy the self-extracting archive that you created as described in Chapter 14 "Distributing Your Installers". +
- +If you are providing a Linux tar file for network download, you need to copy the Linux tar file from the
Outputdirectory. +
- +If you are preparing a Windows installer, put the
Setup.exefile for your Windows installer one level above the download directory. For example, if the download directory isMozilla/download, put theSetup.exefile in theMozilladirectory. + ++
++ +In addition to setting up the download directory, you should provide instructions on your web site for each type of installer available. +
++ + +End-User Instructions for Windows +
+ + ++ +Instruct your Windows users to follow these steps: +
++ +
+- +Create a new folder on their hard disk. + +
+
+ +- +Download the
Setup.exeto that new folder from the FTP location provided by the ISP. + ++
+ +- +Double-click the
Setup.exeto install Mozilla 1.4.1. + ++
+ +- +Delete the new folder when installation is complete. + +
+
++ + +End-User Instructions for Macintosh +
+ + ++ +If you are providing a Macintosh Mac OS 9 installer for network download, instruct your Macintosh users to follow these steps to install Mozilla: +
++ +
+- +Download the self-extracting archive from the FTP location provided by the ISP. + +
+
+ +- +After the file downloads and extracts itself into the Mozilla Full Installer directory, double-click the Mozilla Installer file to install Mozilla. + +
+
++ +If you are providing a Macintosh Mac OS X binary for network download, instruct your Macintosh users to follow these steps to install Mozilla: +
++ +
+- +Download the self-extracting archive from the FTP location provided by the ISP. + +
+
+ +- +After the file downloads and extracts itself, double-click the file Mozilla Installer file to run Mozilla. + +
+
++ + +End-User Instructions for Linux +
+ + ++ +If you are providing a Linux binary for network download, instruct your Linux users to follow these steps: +
++ +
+ +- +Download the Linux tar file from the FTP location provided by the ISP. + +
+
+ +- +Untar the tar file. + +
+
+ +- +Go to the directory
mozilla-installer. + ++
+ +- +Run
./mozilla-installerto install Mozilla. + ++
+ +- +Delete the
mozilla-installerdirectory when installation is complete. + ++
+
++ + + + + diff --git a/mozilla/cck/CCKDocs/gifs/button.gif b/mozilla/cck/CCKDocs/gifs/button.gif new file mode 100644 index 0000000000000000000000000000000000000000..33435328567f32d6d18eb119e09321ede2190a92 GIT binary patch literal 6855 zcmZ|TXHXO0_b~9KrxBv4fOPeXR3%s-RzyV!iijW*ijjz*Q3!?}fvBN}A~p0NMx+EH z7
+
+ + + + + + + + + + + + + + + +
+Copyright © 2003 Netscape Communications Corp. All rights reserved.
+
+Last Updated October 05, 2001
+
Coyg*V 3SRTK1_dL&
ze^dWX!h)vag_C8%A7e6ep~9b6gp*@3OE-nHr-eUqx7Ocok?33hsi6xn&DsggLDxQ^E=dsA9&+qjR
zFFN&XvGm75(9?l-o=z~%UnBn9R@C{>
bKJ6(LZ7Y|
zEcNRPjbq>LTqkkvUcde`6c3)N_VU-s^G07@{d)G>&%?*