incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache OpenOffice Community > Win-en-x86-Setup
Date Tue, 27 Dec 2011 15:33:00 GMT
Space: Apache OpenOffice Community (
Page: Win-en-x86-Setup (

Change Comment:
Touch-ups, adding anchors and TOC

Edited by Dennis E. Hamilton:
h1. Windows Full Install (English x86)

h4. Content
1. [Initial Conditions|#h1]
2. [Initial Configuration|#h2]
3. [Download Presence|#h3]
4. [Installer Startup|#h4]
5. [Setup Installation|#h5]
- 5.1 [Verification of the setup installer|#h5.1]
- 5.2 [Setup installation preparation|#h5.2]
- 5.3 [Selecting setup location|#h5.3]
- 5.4 [Selecting setup unpacking|#h5.4]
- 5.5 [Unpacking the setup|#h5.5]

6. [Perform Setup|#h6]
- 6.1 [Installation wizard startup screen|#h6.1]
- 6.2 [Identify user and select installation account(s)|#h6.2]
- 6.3 [Choose setup type|#h6.3]
- 6.4 [Ready to install the program|#h6.4]
- 6.5 [Installation progress status|#h6.5]
- 6.6 [Internationalization cross-talk/defects?|#h6.6]
- 6.7 [Completion of installation|#h6.7]
- 6.8 [Confirmation of installation|#h6.8]

7. [Post-Installation Observations|#h7]
- 7.1 [Desktop changes|#h7.1]
- 7.2 [First-run and main window|#h7.2]
- 7.3 [About dialog|#h7.3]

h2. 1. Initial Conditions

# The first build tested from Apache OpenOffice is identified as 3.4.0 OOO340m1
(Build:9584).  Is is the 2011-12-15 [Developer Snapshot|]
uploaded by Raphael Bircher.  The file is identified {{OOo_3.4.0_Win_x86_install_en_US.exe}}.
# The installation begins with the installer downloaded to a file location from which it can
be executed.

h2. 2. Initial Configuration

There are many variations of initial configuration that matter.  This first run-through of
the typical scenario is not the simplest but accounts for possible interactions with existing

This instance of the scenario is using a configuration of Windows Vista that already has three
other ODF-supporting applications installed:


h4. 2.1 Observations

* The previous version of is OO.o 3.3.0-it, installed as an experiment around
differences in UI and writing aids.  It was already noticed that the 3.3.0 install stole the
file associations that had been previously associated with the Libre Office installation.
* The shadowed-button works well as a desktop icon/shortcut.  I don't link the tint that much,
but it is a recognizable, simple icon that seems useful to preserve.  Taking it through a
transition that blends in some sort of Apacheness over time would be interesting along with
the march to ASF Top-Level Project.
* The processing model for this case is with Windows Vista Ultimate SP2 (32-bit) installed
on a Windows Virtual PC under Windows 7 Ultimate.  The processor is an Intel i7-980X.  --
dh:2011-12-20T00:11Z.  The virtual display is VGA there's no Aero.
* The account used has administrator privileges.

h4. 2.2 Issues/Migration

* The name associated with the desktop icon/short-cut of course.
* The tooltip acknowledges Oracle support.  The other text is fine.
* This is worth describing with regard to our own build status.  I record it here as part
of capturing observations when they occur (for now). -- dh:2011-12-18T22:19Z

h4. 2.3 Variations

* Different versions of Window
** The next version of Windows available for testing
** The oldest supported platform
** One older than the oldest supported platform (for the purpose of determining what the failure
is like, if any).
* Different processor/platform combinations
* Different combinations with no related applications/dependencies installed, with other applications
installed --dh:2011-12-22T05:51Z
* Different previous user configuration cases
** Installed for all users or one (different?) user account
** Individual user configuration choices and options
** Individual users extensions and (different) user ones -- dh:2011-12-27T00:32Z
* -TODO: Complete the reporting on all confirmation screen-shots and their annotation-
* -TODO: Place anchors on all sections where there may be associated bug reports- -- dh:2011-12-27T15:26Z
* *TODO:* Create bugzilla reports for issues noticed so far -- dh:2011-12-27T02:09Z
* -TODO: Add a table of contents at the top, listing and linking to the stages- -- dh:2011-12-27T15:27

* *TODO:* Find existing bugzilla reports that apply to this part of deployment.
* *TODO:* Blend in the observations from "eric b" and makes sure all of them are reflected
* *TODO:* Seach Wiki, Web site, and Forums for relevant material.

h2. 3. Download Presence


h4. 3.1 Observations

* The button icon with download arrow works very well at the small (detail) size.  
* I added a date to the beginning of the downloaded file name to help me differentiate different
builds.  I got the date of the build wrong, but it works as a differentiator for the download
and these screenshots anyhow.
* the larger button icon is great too, used in the lower left of the Windows Explorer window.
 It is obscured because more than one file is selected.
* the "modified" date is the local time and date when it was downloaded in this case.
* This file location is at a UNC path (i.e., \\Whs\...) to a shared folder on a file server.
 These work fine and I don't expect any regression. -- dh:2011-12-19T00:13Z

h4. 3.2 Issues/Migration

* (none)

h4. 3.3 Variations

* Installation from a thumb drive
* Setup from a CD-ROM
** Simply as a file-system source
** As an Autorun installation
** As a gold disk with enterprise setup
* Over-network enterprise installation 
* TODO: Check the different explorer views of the installer to see how the icon may change
-- dh:2011-12-27T00:13Z

h2. 4. Installer Startup

Installation was initiated by double-clicking the downloaded installer file.


h4. 4.1 Observations

* There are three kinds of warnings that can occur at this point.  First, files that are downloaded
from the internet may provoke a warning before execution is allowed.  Secondly, there is some
verification of the EXE (which is a problem in this case).  Finally, there is a requirement
for administrative operation of the installer.  This message reflects at least the last two
of those cases.
* The nightly builds are not signed.  

h4. 4.2 Issues/Migration

* A signed .EXE is needed
** It would be valuable for any downloadable binary to be signed although this might not work
with automated nightly builds.  
** A process and appropriate ceremonies for binary releases is needed that includes signing
the binary in the form that is verified by Microsoft Windows.
* The different "Compatible with Windows _X_" guides might need to be checked to determine
other practices that are part of establishing that the product is considered clean enough
for installation on whatever X is expected to be workable. --dh:2011-12-22T05:57Z

h4. 4.3 Variations

* Installation that doesn't require elevated privileges?
** How failure happens when installation is attempted without sufficient privileges
* Setup of a portable version?
* Different initiation and account conditions
** Run As Administrator from a non-administrative account
** Running from a command-line session with and without administrative privileges
** Running from alternative shells
*** Powershell
*** 3rd part shells
*** Software for Unix Applications (SUA) bash shell
*** Cygwin bash shell

h2. 5. Setup Installation

The download sets-up in two stages.  The configuration for setup is extracted from the installer
executable and then setup is executed.  This can be mystifying.  (See observations in conjunction
with the different dialogs.)

h3. 5.1 Verification of the Setup Installer


h4. 5.1.1 Observations

* Here three sizes of the download button image can be seen:
** in the detail of the installer listing in Windows Explorer
** in the simple splash that is shown while the installer is being verified
** in the expanded detail about the selected file shown at the bottom of the Explorer window
(with super-imposed elevated-privilege marker) on the ones displaed by Windows itself
** It strikes me that variations of these buttons with an Apache feather in the lower-right
would be an interesting possibility also. --dh:2011-12-22T05:59Z
* These can be retained without difficulty and perhaps tuned slightly for differentiation
to reflect Apache OpenOffice migration to a Top Leve Project.
* This verification process is against damage to the installer.  It is separate from authentication
of a signed executable or an external check (MD5, external signature, SHA1, etc.).

h4. 5.1.2 Issues/Migration

* Nothing critical

h4. 5.1.3 Variations

* Presumably an install from CD-ROM or a flash drive might skip much of this and work with
setup folders directly.  There are more variations listed at that point.
* The message needs to be internationalized for different set-up languages
* The message might need to be different because of the difference between installer and setup.
* TODO: See if there are variations in message appearance related to desktop theme and display
model on different Windows setups

h3. 5.2 Setup Installation Preparation

Once the installer is verified, it is discovered that the first stage is not yet complete.


h4. 5.2.1 Observations

* This is the first clue that we aren't doing setup yet, what has happened is that the setup
installer has been verified and is now going to operate.  The sequence of displays should
be reviewed for consistency.
* The separation between what the installer installs and then what setup does could be clarified.
 It is not clear how this could be blended in better though.

h4. 5.2.2 Issues/Migration

* Dialog Title strip
** The download button symbol appears in the left of the title band at the top of the dialog
window.  This can be retained.
** The title of the dialog needs to be updated to identify what Apache OpenOffice version
installation is being prepared.
* The left column has material that must be replaced for Apache OpenOffice
** Replace the and gulls logo at the top of the column.
** The standing gull button with shadow is useful to keep. 
** The Oracle name at the bottom of the left sidebar needs to disappear.
* The text column needs to be updated to refer to the correct product and version
** The Thank you needs to be reworded.
** The mention of in the first paragraph needs to be changed.
* There is no functional change, it is just static content that needs to be corrected.

h4. 5.2.3 Variations

* The different internationalizations
* Possible avoidance with installation from pre-built setup folders as on CD-ROMS, thumb drives,

h3. 5.3 Selecting Setup Location

Now it gets very confusing.  When the "Select Folder" dialog comes up next, I immediately
go into the Browse option.  Here I am setting up a new folder in the same UNC location that
I downloaded the installer to, identifying which installation I am using it with:


h4. 5.3.1 Observations

NOTE: I did not capture the Select Folder dialog before I browsed for a folder location. 
I will compensate for that after this screen.  -- dh:2011-12-20T02:06Z

* The browse to a folder to use has a straightforward dialog.
* Navigation onto the network, to a server, and then down to the folder is a bit cumbersome
because this doesn't have an Explorer view.
* If I hadn't been doing this for a lot of OpenOffice-based installations, I would not know
whether the folder I choose will receive files (yes) or will it receive a folder so it is
safe to use a folder that already has other material (no).

h4. 5.3.2 Issues/Migration

* The title bar of the "Browse for Folder" dialog is fine, still using the download button.
* The text names the product and version and that needs to be changed.
* This is _not_ really that is being installed.  It is the setup that is being
installed.  That needs to be very clear (and another reason for reviewing the nomenclature).

h4. 5.3.3 Variations

* This examples uses a UNC location on a local-area file server.
* Installing setup on a CD-R/W drive might be interesting.
* Installing setup on a flash drive would also be useful.
* I assume that a CD-ROM install would already have the setup expanded into a folder that
auto-run or a manual setup execution could use.  It would be interesting to confirm that this
is an easily-constructed variation for future re-install, installation on multiple systems,
* Check Failure Modes
** If the selection or folder created is incorrect in some way, verify that the failure is
resilient and, ideally, can be backed out from.
*** Improper characters in a new folder or folders names
*** Access authorization issues
*** Creating a too-long path/file name in the dialog or as the result when the setup files
are unpacked -- dh:2011-12-27T01:40Z

h3. 5.4 Selecting Setup Unpacking

At this point, it is the setup files that are being installed, not itself.
 This is how that appears before the unpack is started:


h4. 5.4.1 Observations

* This dialog first appears with a default (pre-filled destination) that is on the users _desktop_.
 This is an absurd location:
** Most users don't think of this as part of the file system (though some very naive users
put everthing on their desktop).
** There is no indication of the consequences of a particular choice or whether there is some
special reason for defaulting to the desktop.
** It is not clear whether the folder can be safely deleted without causing difficulties.
 At one point I found out that installing a later version would fail if the previous setup
were removed, because it was needed to uninstall the previous version.
* For those reasons, I have adopted the practice of putting setup folders on a shared server
location where I keep them for an extended period of time without cluttering my desktop.
* I have let this software train me to treat this as ordinary and, while I remark on it to
myself every time I do an OO.o install, I have come to step through it without question. 

h4. 5.4.2 Issues/Migration

* There's something off about involving users in this at all.  Not knowing the reason for
it and the consequences of choices is unfortunate.
* Dialog Elements
** The product name needs to be changed in the title line of the dialog box.
** The product name and version is mentioned twice in the instructions.
** There is an logo and gull symbol in the top heading area.
** There is a faint identifier of the Nullsoft Install System v2.37 that might need updating
if not supplied automatically
** The space-available number is not exactly right, since this is a virtualized file system
with over 6 TB installed drive space having 4.4 TB free.  This could be what is reported by
the server, though.
* The setup folder is beiing placed at a UNC address and it should work well from there. 
Previous OO.o and LO releases operate with this just fine.
* Unless the setup files do have to be retained for some future purpose, the default destination
should be to a generated temporary location and no alternative should be directly requested
unless some minimum-space-available threshhold cannot be met.  It would be useful to have
a way to specify where the setup goes, but as an exception and not one that has casual users
deal with a dialog for which the consequences of any choice are not understood.
* It is particularly important that users not be confused into thinking that this has anything
to do with where Apache OpenOffice itself will be installed.  

h4. 5.4.3 Variations

* none?

h3. 5.5 Unpacking the Setup

Now the setup files are being unpacked into a place where the setup can be run.


The "Show Details" display provides a running log of the unpacking and initiation of the execution
of the next stage.


h4. 5.5.1 Observations

* This is simply the process that extracts the files from the installer into a folder of all
of the artifacts that are needed for setup.
* It should have been far easier to get to here.

h4. 5.5.2 Issues/Migration

* The dialog title strip and the top titles are essentially the same as for the previous dialog.
 The name and summary message have changed.  It is now about Unpacking.

h4. 5.5.3 Variations

* *TODO:* Examine the unpacked folder of setup files and sub-folders.
** Check for licenses, readme, and other text files
** Check for uses of brand names, versions, etc.
* Try starting from the installed setup files, with the various variations for initiating
* *TODO:* Consider the importance of signing the expanded setup configuration because it is
a point of customization and rebranding by derivative distributions. -- dh:2011-12-27T00:50Z

h2. 6. Perform Setup

When the setup files are installed, setup is carried out by the "Installation Wizard."

h3. 6.1 Installation Wizard Start Screen


If the space requirements are satisfied, there is an option to proceed:


h4. 6.1.1 Observations

* Note that there is no "<Back" option from here.  This is a new, independent execution
of the setup software.
* It is not clear what the size requirement is.  Also, it is not clear how that is impacted
by changes not yet made as part of selecting a custom installation.  
** This is also independent of the size requirement and available-space determination for
installation of setup, as opposed to what is now required for installation of the build itself.
-- dh:2011-12-22T06:04Z

h4.  6.1.2 Issues/Migration

* The sidebar has an entirely different image and theme than the setup-installation stage
in the preceding section.  The same theme should be continued here.
* Release-specific elements
** The dialog title bar now has the Microsoft installer icon.  The title itself needs to be
updated for the Apache OpenOffice release/nightly.  It would be great if this could be Setup
Wizard instead of Installation Wizard.  Or, generally, the nomenclature should be smoothed.
 There may be a Microsoft style and internationalization that applies here.
** The Welcome title needs to be repaired as well
* On the second dialog, with clickable "Next>", there are two paragraphs to be customized:
** The first paragraph uses "Installation Wizard" and the name of the release.
** The second paragraph acknowledges a build contribution.  This should be paraphrased or
** The second paragraph refers to a {{}} page that provides contribution
credits.  If this is to be continued, the page that is reached needs to be structure differently.
** TODO: Take a look at that page or any alternative. -- dh:2011-12-22T06:17Z

h4. 6.1.3 Variations

* Determine where the boundary is for the space-check detecting too little space for an installation.
** Find just too small and just large enough boundaries.
** Confirm what the message is when there is insufficient space.
** Check to see if this conforms to the requirements for a typical installation. -- dh:2011-12-22T06:18Z

h3. 6.2 Identify User and Select Installation Account(s)


This single dialog combines two separable configuration cases:

* Identification of an User and Organization
* Determination of the account(s) for which the software is installed

h4. 6.2.1 Observations

* There are two places where the product name and version appear
** In the title bar of the continuing Instgallation Wizard dialogs
** In recessed style in the horizontal line above the back, Next, and Cancel buttons
* There is an logo on the right end of the title band for the specific dialog.
* It is not clear how the User Name and Organization work when the software is installed for
all users.  
** It appears that the information is for the current account (see below).
** Sometimes first-run in additional accounts will present some setup options.  It is not
clear whether OO.o setups do this.

h4. 6.2.2 Issues/Migration

* *BUG* For as long as I have been installing and LibreOffice software, this
dialog is incorrect.  The "Only for me" provides the wrong account name.  However, it will
be installed under the correct account if this option is selected.
** It appears that the first account established on the OS is always listed.  In my case,
this is invariably an account named 'admin'.  This is generally not the account in which I
install software for application work.

h4. 6.2.3 Variations

* Take the "Anyone" case
** See what happens when other individual setups also exist
* See what happens when a previous installation was "Anyone" followed by an "Only me" for
a later version.
* See if earlier versions can be installed in an account if there are later versions set up
for other accounts.
* Consider other out-of-sync product/version cases.
* Consider the case when other "Only me" or an "Anyone" has different localization and internationalization
and their specific extensions
* Check Failure Modes
** Too-long entries for User Name or Organization?
** Character set limitations for User Name and Organization?
*** Try special characters that may have difficulty when encoded in XML element or attribute
values -- dh:2011-12-27T01:43Z

h3. 6.3 Choose Setup Type


h4. 6.3.1 Observations

* The appearance of product and version information is the same as on the previous Installation
Wizard dialog frame.
* This install uses the default "Typical" setup type.  
* There's that setup word again.  Three times on this dialog frame.
* It is worth mentioning that one can backup and change the Setup Type.  It is useful to select
Custom just to see what is selected for the default/Typical.

h4. 6.3.2 Issues/Migration

* None

h4. 6.3.3 Variations

* *TODO:* Take the Custom option and explore its impact, what the different selections provide

h3. 6.4 Ready to Install the Program


h4. 6.4.1 Observations

* This is the obligatory "Are You Sure?" point, although it is possible to cancel the started
setup process.
* There does not appear to be a review of configuration and installation choices.
* The product and version dialog elements are the same as for the previous two frames of the
Installation Wizard dialog.

h4. 6.4.2 Issues/Migration

* None?
* *META-BUG* Confluence Wiki doesn't show the selection of images properly as this many are
added to the page.
** This doesn't happen on all cases.  The edge case may have to do with how full the rows
are and when scrolling of the rows of images starts.

h4. 6.4.3 Variations

* Don't create a link
** See if existing links are removed in this case
* Back up to earlier dialogs and see that the next path comes through clean
** Switch from Custom to Typical setup type
** Switch the Setup User Location(s)
** Vary other details, such as installation folder for the software

h3. 6.5 Installation Progress Status


The installation screen reports stages and uses progress bars.


h4. 6.5.1 Observations

* Now there are five places where the product and/or version are mentioned.
* The variation from dialog frame to dialog frame is only in the Status: description and the
progress bar.
* Note that there is no Back or Next exit while this happens, only Cancel.

h4. 6.5.2 Issues/Migration

* None?

h4. 6.5.3 Variations

* Cancel the installation at various stages and see what the exit/recovery process is
* Explore what is left on the system
* See if resumption via the saved setup installation works

h3. 6.6 Internationalization Cross-Talk/Defects?

Here, there is an odd situation.  A series of dialog frames provide status descriptions in





h4. 6.6.1 Observations

* The suspicion is that the incorrect language for these messages is a function of the previous,
3.3.0 version, being an Italian-language localization.
* These messages seem to reflect that the previous version is being removed and that its uninstaller
is performing the work.

h4. 6.6.2 Issues/Migration

* *BUG:* The incorrect source of these messages is a problem.  If it is a dependence on the
previous-version uninstaller there are other potential difficulties.

h4. 6.6.3 Variations

* See what happens when a previous, different-localization has already been removed or is
set up for a different user(s) combination.

h3. 6.7 Completion of Installation

The status descriptions return to English:


This appears to be the actual setup of the downloaded build now:


Sometimes there is no status to speak of:


h4. 6.7.1 Observations

* The product and version content is the same for all of these dialog frames, just as with
the Installation Wizard frames before them.

h4. 6.7.2 Issues/Migration

* None?

h4. 6.7.3 Variations

* All of these stages present occasions to determine how well the Cancel button works.

h3. 6.8 Confirmation of Installation


h4. 6.8.1 Observations

* The initial panel layout of the Installation Wizard has returned.
* There are but two places where the product and version are mentioned:
** In the title bar of the Installation Wizard dialog box
** In the text with announcement that installation has successfully completed.
* There is nothing to do with this dialog but click Finish.
* There was no indication of a license, any readme, or other options of that kind

h4. 6.8.2 Issues/Migration

* None?

h4. 6.8.3 Variations

* None?

h2. 7. Post-Installation Observations

h3. 7.1 Desktop Changes


h4. 7.1.1 Observations

* The previous, 3.3 icon has been removed.
* The new icon identifies 3.4.
* The tool-tip for the 3.4 icon contains the name of the product, its version, and credits

h4. 7.1.2 Issues/Migration

* The development builds should not replace existing non-development builds.
** *TODO:* Capture the bugzilla already created about this.
* The Apache OpenOffice builds should not automatically replace any existing installations
of releases from other projects with their different licenses and deployment processes.
* The Apache OpenOffice installation must be careful what previously-installed material is
relied upon because of language, user preference, and osmosis of incompatibly-licensed work.

h4. 7.1.3 Variations

* *TODO:* Review the installation in the Start Menu
* *TODO:* Review the installation in the Windows file system
** Verify both FAT and NTFS
* *TODO:* Review the installation in the add/remove programs control panel displays
* *TODO:* Review the installation in the Windows Registry

h3. 7.2 First-Run and Main Window


h4. 7.2.1 Observations

* This is the main page of the overall application, reached by the desktop icon.
* The ODF-grey icons/insignias are used.
* The logo and version 3 is used (instead of 3.4).
* The gull button with shadow works
* The tool tip for one of the bottom symbols is shown

h4. 7.2.2 Issues/Migration

* It seems straightforward to replace the logo and version with the Apache
OpenOffice replacement.
* The button is nice to preserve.
* The ODF-grey icons are misleading, since what is opened is not a document of fixed format,
but an application that can produce varieties in their classes of formats

h4. 7.2.3 Variations

* Colored icons/insignias are being proposed.
* *TODO:* Link to the discussion of icons and of logos on this wiki
* *TODO:* Include some images on the contrasting use of the ODF-grey in the icon discussion,
to illustrate the different ways the icons and their variations show up.

h3. 7.3 About Dialog


h4. 7.3.1 Observations

* The main application screen has the icon and the ODF-grey icons for launching
the individual applications.
* The Help | About dialog has the following product and version aspects:
** The text and gull icon is present
** The identified stage is version "3", not version "3.4"
** The gull button with shadow works
** The version is identified as 3.4.0
** The build number does not advance
** A Copyright notice reflecting Oracle and its affiliates (with start and end dates) is shown.
 There is no indication, in this case, that only some rights are reserved and there is an
available license.
** There is an Oracle identification and linking to a web page of credits to contributors.

h4. 7.3.2 Issues/Migration

* Action is required with regard to the credits.
* The Oracle claim needs to be replaced by the similar Apache one that avoids copyright notice.
** Whether the Oracle copyright needs to be reflected somewhere, it should be in linked material
** There needs to be linkage to license and readme/release-note information
** The About panel is an ideal place to introduce the incubating logo and also the Apache
Incubator Project feather and link, perhaps at the bottom of the text panel.

h4. 7.3.3 Variations

* *TODO* Explore the remainder of the Help menu for version and producer/product dependencies.
* *TODO* Check out the accessibility support
** The installation process and different stages
** The main page and its tool-tips and dialogs -- dh:2011-12-27T03:41Z

Change your notification preferences:

View raw message