Page History

...

• 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

  Issues/Migration

• none

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

...

• There are three kinds of warnings that can occur at this point. First, files that are downloaded form the internet may receive 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.

...

• Installation that doesn't require elevated privileges?
  • How failure happens when installation is attempted without sufficient privileges
• Setup of a portable version?

Installation Setup

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.

Verification of the Installer

Image Added

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
• 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.).

Issues/Migration

• Nothing critical

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.

Installation Preparation

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

Image Added

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.

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 OpenOffice.org 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 OpenOffice.org in the first paragraph needs to be changed.
• There is no functional change, it is just static content that needs to be corrected.