Proposal for a StarOffice / OpenOffice.org 6.0 Setup Feature List

Version 1, 02/16/2001, Leyla.Schroeder@germany.sun.com

Priorities:

1 – Must

2 – Should

3 - Can / Nice to have

Installation in General

Area

Description

Priority

CD / AutoRun

AutoRun should be supported under Windows

1

CD / Introscreen

An introduction screen should offer installation of the programs that are available on the CD:

  • StarOffice / OpenOffice.org 6.0

  • Acrobat Reader

  • Java Runtime Environment

Furthermore, links to additional information should be offered:

  • Documentation

  • Patches (for Solaris)

3

Download / Customization

Download packages should be generated during online-connection to include only those components, the user selects in his session. Therefore we need a tool to create a binary installable file which includes only the required modules.

3

Installation package

The different installation packages should only show those files to the user, that are important to him:

  • setup.exe

  • readme.txt

  • lincense.txt

  • jre-(...).exe

  • setup.inf

The installation files (f_00xx) should be moved to a sub-folder.

1

Setup / Wizard

The setup should run in window mode, not full screen. The new wizard only consists of sequenced dialog windows.

1

Setup / Design

The design of the setup dialogs must be worked over (=> white background with Sun colors).

1

Setup / Help

Pressing the Help button should open the Help in a second, resizable window. For the display our own Textengine (MultiLineEdit) should be used.

2

Setup / Readme

For displaying the Readme in a more readable form, an additional button should be offered in the dialog that opens the Readme in a HTML view.

If no browser exists on the system, the button is disabled. Here only the view in the text field of the dialog is available. (The txt format of the Readme must still exist in the installation package.)

3

Migration

A migration 5.2 => 6.0 should include:

  • User-defined AutoCorrect settings

  • User-defined AutoText modules

  • User's Basic macros

  • User-defined gallery themes

  • User-defined templates

  • User-defined dictionaries

  • User's AddIns

  • User's Workfolder

  • Database migration including:
    - Addressbook data
    - Bibliography data

  • User's configuration data (from user/config), including:
    - Palettes
    - User-defined Math symbols
    - User data
    (Further configuration data has to be defined in detail.)

1

Languages / Program

An installation package for multiple languages is needed for the OEM version.

Thereby choosing a language is valid for the program language (for menus, dialogs) and the document language (samples, templates).

Changing the language after installation should be possible via setup (modify installation).

2

Languages / linguistic (CJK)

The Standard installation installs a default set of languages for the linguistic. This set depends on the Office language to be installed. Here the language modules for the CJK version must be re-defined.

1

Languages / linguistic

AutoText and AutoCorrect data must be written language dependent into the installation.

1

Languages / linguistic

The languages for the linguistic that are installed should include not only spell checking, thesaurus and hyphenation but also language-dependent AutoText modules and replacement and exception settings of AutoCorrect.

1

Installation path

The default installation path should be:
$:\Programs\(%Productname)60 under Windows
\home\(UserID)\(%productname)60 under Linux/Unix

The variable stands for StarOffice60, OpenOffice60, StarSuite60.

If using the variable is not possible, the installation path has to use "Office60" instead of the product name.

1

Installation space

The user should get more information about the available space when selecting the installation path. (=> list box with devices and available/estimated required space)

As we cannot show how many space is really needed for a customized installation as long as the user has not selected the modules to be installed, here the installation path has to be determined by the user after selecting the modules.

2

Dialog buttons

Button for starting installation/deinstallation must be renamed from "Complete" to "Install"/"Uninstall"

1

Java setup

The user should be better informed for what installing the JRE is good for (Applets, Java services). For this the setup dialog should give a hint and/or the help must be improved.

3

Progress bar

During the installation process a progress bar appears with text display for actual process description.

1

Install on demand

Features, that are not installed yet, will be installed on demand. Thereby the needed files are left on the source (CD or network share) and can be copied down automatically the first time they are used.

The user's workflow will not be aborted by this process.

(It is not clear, if this feature can be realized.)

1

File type info

If more than one installation exists on the system, the file type info should be assigned to the latest installation.

Done

Adabas

Adabas must be re-integrated in the setup.

1

Custom Installation

Area

Description

Priority

Module selection

The user may not be allowed to deselect something, that is necessary for a feature/component to be installed.

1

Subtree icons

Icons in the subtree should be replaced by more meaningful ones.

2

Module descriptions

Module descriptions must be improved

2

Languages / dictionaries

The dictionaries of the add-on folder must be included in the setup to offer more than 5 languages.

1

Filterlist

The filterlist must be reviewed and updated.

1

Fonts

It must be clear to the user which fonts will be installed and for what they are needed. For this a font list must be offered that shows all fonts to be installed (same as Writer / Textfilter Im/Export). Selecting a font entry would display a description.

2

Product name

The module selection list box should use the variable for the product name like:

- %Productname components

+Writer
+Calc

Whenever the product name itself is clear, we can use just the short names (Writer, Calc etc. instead of %Productname Writer, %Productname Calc). Thus the variable is necessary only the first time.

1

Summary

Before starting the installation the user should get a summary of the settings made.

3

Change / Repair / Deinstallation

Area

Description

Priority

Control Panel

Win95/98/NT:
When starting deinstallation from the Control Panel's Add/Remove Programs of Windows the option Deinstallation must be selected as default. (Windows only)

Win2000:
Here we should offer one Change and one Remove button (instead of Change/Remove). When Change is selected, the default option is "Change installation", when Remove is selected, a message box should appear to ask, if StarOffice / OpenOffice.org really should be deleted.

3

Restricted User

Under W2000/NT installation, deinstallation and changes of the installation are not allowed for restricted users and may not be possible.

1

File Deletion

All program files and folders of the StarOffice / OpenOffice.org installation must be deleted when deinstalling, only those created or modified by the user remain on the disc (unless, before starting the deinstallation, the user explicitly states that these files have to be deleted, too).

1 (Windows)

2 (others)

Repair / Description

Option is often not understood, must be made more transparent (change text).

1

Repair / Source

Repairing from CD should be possible.

2

Network installation

Area

Description

Priority

/net

For calling a network installation we should offer a new possibility (in addition to using DOS box + /net). For this clicking on setupnet.lnk starts network installation:

  • setup.exe (calls single-user installation)

  • setupnet.lnk (executes the command "setup -net")

Changing an installation should be possible via double-clicking on the setupnet.lnk, which must remain on the CD)

1

Multilingual version

Installing StarOffice / OpenOffice.org in more than one language should be possible for the network installation. The administrator can choose the language to be installed from all available languages that we offer. The user can choose his language from this sub-set. Only one language can be selected by the user. Thus he should be able to change it later by the setup.

=> The workstation installation needs a page for choosing the language.

1

Naming

The workstation installation offers the two options "Standard Workstation Installation" and Standard Installation local".

These options should be renamed to

  • Workstation Installation

  • Local Installation

2



1