incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache Community > Win-en-x86-Setup
Date Thu, 22 Dec 2011 06:25:00 GMT
Space: Apache Community (
Page: Win-en-x86-Setup (

Change Comment:
More touch-ups and text for Installation Wizard Start Screen

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

h2. 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. 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. 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. 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. 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

h2. Download Presence


h4. 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 work 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. Issues/Migration

* (none)

h4. 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 

h2. Installer Startup

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


h4. 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. 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. 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. 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. Verification of the Setup Installer


h4. 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. Issues/Migration

* Nothing critical

h4. 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.

h3. Setup Installation Preparation

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


h4. 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 operation.  Or perhaps the installer setup
is now going into operation.  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. 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. Variations

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

h3. 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. 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. 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. 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,

h3. Unpacking the Setup Files

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. 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 cleaw 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. Issues/Migration

* There's something off about involving users in this at all.  And 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 with 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. Variations

* none?

h3. 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. 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 easier to get here.

h4. 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. Variations

* Examine the unpacked folder of setup files and sub-folders.
* Try starting from the installed setup files, with the various variations for initiating

h2. Perform Setup

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

h3. Installation Wizard Start Screen


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


h4. 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.  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.  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

Change your notification preferences:

View raw message