Slim Install Project » UI Specification
en

UI Specification

Slim - New Solaris Installer UI Specification Frank Ludolph  August 2, 2007

Contents:

IntroductionTarget Users

UI Design
   Visual Design
   Accessibility
Screens
   Navigation
   Splash Screen
   Welcome
   Disks
   Time Zone, Date and Time
   Users
   Software
   Installation
   Install Progress
   Finished
   Install Failed

Introduction

Slim is the second release of the New Solaris Installer (NSI) and builds on Dwarf which was first released as the installer for Solaris Express Developer Edition 9/07. This user interface specification has been updated from the original Dwarf specification. (Items new to Slim are marked "[S]". This is the complete written UI specification for the Slim release of NSI. Features new to Slim are specifically called out at appropriate points in the text. Slim is an OpenSolaris project.

One of the primary issues faced by users installing Solaris is downloading. The current Solaris Express iso file (DVD image file) is about 3.5 GB. Due to the limitations of some file systems, the iso is split into three parts which the user must download separately, assemble and burn to a DVD. The focus of Slim is a LiveCD based installer which will be much smaller and thus faster and easier to download and burn to a CD. Tthe user then boots a CD directly into Solaris running a live GNOME desktop without first having to install. The environment provides various applications, including a browse The network is auto-configured during boot to enable network access. The user then explicitly starts Slim when ready to install Solaris. Slim will use the network connection to pull down many of the packages to installed from a network-based repository. Note that Slim and the other LiveCD elements and the repository could be stored on a bootable DVD for use when a network is unavailable or otherwise inadequate. An end-user scenario is available on the Caiman OpenSolaris project,

Slim's new features:

  1. LiveCD based - user will manually start the installer from a desktop icon
  2. Networked - packages, documentation, release notes, etc. will be available from well-known network-base repositories
    1* Slim must be able to run from a LiveDVD on a non-networked machine
  3. ZFS - Slim will create ZFS file systems and data sets. The old UFS is not supported.
    1* Conversion and upgrading of existing UFS Solaris environments will be supported
  4. Snap upgrade - a successor to Live Upgrade will be the only upgrade mechanism supported. This is a separate OpenSolaris project that will be integrated into Slim

Target Users

The target users for Slim are developers. Sun would like to attract more developers to working on Solaris and using Sun tools, e.g. Sun Studio and Net Beans. Difficulties of downloading and installtion onto a wide range of x86 hardware and the overall installation experience are considered to be inhibitors to adoption. Recent work to include more drivers into Solaris Express (Nevada) has mitigated the hardware issues, and efforts continue. The Desktop has also been modified to include links to developer-specifc documentation and Launch menu entries for the tools. The current Solaris installer has been trimmed the number of questions and now automatically includes the tools, however the overall user experience, while improved, still looks like something from the early '80s. Slim will graft a modern graphical UI onto the current installer engine. Future versions of Caiman will slowly replace the installer engine with a more modern machanism.

UI Design

The Slim UI should have a modern graphical appearance and interaction, consistent with Sun's current brand guidelines and look and feel. As such, Slim will utilize the Nimbus look and feel theme that has been recently implimented for Sun's GNOME-based desktop.

Slim has only a GUI UI. A text-based UI will be added in a future release. This is a requirement for the final version.

Visual Design

The layout should follow the following relevant guidelines:

  1. Sun Brand Guidelines
  2. GNOME Human Inteface Guidelines
  3. Java Look and Feel Guidelines

The precise size of the window will be determined and adjusted by each localization based on its language requirements. The installer must be able to adjust to different window sizes and layout the various components appropriately. For example the buttons should always be a fixed amount from the bottom and edges of the windows, regardless of the window size.

Screen designs and layout templates for 800x600 and 1024x768 screens and for some of the installer screens are available.

Accessibility

[S] The installer is not technically required to be universally accessible as it generally serves a system administration function. System administration functions are currently exempt from Section 508 requirements though that may be changing. However, it is desireable to be universally accessible and the installer will be made so, in stages, over a series of releases. Dwarf supports mouse-less operation. [S] Slim should support themes and the Orca screen-reader for low-vision use.

The applicable guideline is Section 508 Accessibility Guidelines

Screens

The new Solaris installer is wizard consisting of a series of screens. It is designed to support several different operations: Install, Upgrade, and possibly Refresh and Add. In the first release the operations are limited to Install and Upgrade. The user selects the desired operation on the first screen, the Welcome screen. The selected operation determines which wizard screens will be displayed to the user. The set of screens is listed at the left of the screen and each is highlighted in turn as the user proceeds through the wizard.

Behaviors

The following generic behaviors apply to all screens unless noted otherwise:

  • When a screen is displayed the focus should always be set at the first (top-most) control on the screen.
  • Screen default vaules should only be set the first time the screen is displayed. After that it is assumed that the settings are too the user's liking. In particular values should not be reset to defaults after the user has changed them.
  • If a user returns to a screen, it should display the same values as when the screen was last exited with one exception; if the user has made a change to a previous screen that invalidates an existing value on this screen, that value should be set to the valid default.
  • All navigation buttons (below) appear on all screens. One or more buttons may be disabled on specific screens as specified below.

Navigation within the Wizard.

All of the screens contain four buttons: Quit, Help, Back, and Next. They function as follows:

  • Quit: Displays a confirmation dialog, and if confirmed, opens a Terminal window and quits the installer. The confirmation dialog is not posted when the "last" installer screen is displayed. The Help and License windows, if open, should also be closed. The terminal window allows the user to restart the installer or to perform other commands. Dialog: "Do you wnat to quite this installation?"
  • Help: Opens a separate Help window and displays content specific to the current screen. The Help window can remain open while the user moves through the installer. When the user moves to a new installer screen, the help window is automatically updated to display content specific to the new screen.
  • Back: Returns the user to the previous installer screen. The previous screen should display the same content as when the user last saw the screen.
  • Next: First performs any screen specific content checks; error conditions should be checked before warning conditions, from most serious to least serious. The next screen is displayed when there are no errors and the user proceeds in spite of any warnings. If the next screen has been previously seen by the user, its content should be the same as when previously viewed.
Warnings
  1. User clicks Quit: "Do you want to quit Solaris installation?"
  2. [S] User clicks Quit on the Progress screen: [TBD]
  3. User clicks Quit on the Tools or Installation/Upgrade Failed screens: No confirmation warning.

Installer Language

[S] The installer runs in the language set for the desktop during LiveCD boot.

This screen is used to indicate the language used to display information within the Caiman installer. Since an application cannot change its display language after it starts, this screen is actually displayed by a small, invisible (to the user) application which collects the language information from the user and passes it when this application starts Caiman.

Defaults:
  1. English (US) 
Behaviors
  1. The small app behind this screen starts Caiman, passing the language information. Caiman will display nothing until instructed to by this application. 
Errors
  1. There are no error conditions possible

Keyboard

[S] The installer runs in the language set for the desktop during LiveCD boot.

Many keyboards are not self-identifying and so the user must tell the computer the keyboard's layout so that the keystrokes can be properly interpreted. This screen is part of the same small application as the Installer Language screen above. 

Defaults:
  1. Use the keyboard layout stored in the computer's NVRAM if available otherwise dependant on the selected installer language.
Behaviors
  1. Displays the list of keyboard layouts using the language selected by the user in the preceeding installer language screen. This is done by predefining the list in the ten languages then using the appropriate list. 
  2. When the user clicks Next, the small app will hide its window, inform Caiman to display its window, then terminate. 
Errors
  1. There are no error conditions possible
Future
  1. Reform as a simple, narrow, non-branded dialog window. (UIRB TCA 5.1) 

Splash

[S] A splash screen is required when a starting application cannot display another feedback response, e.g. a new opened window, within two seconds of the user initiating the "start" action, e.g. double-clicking on the application's icon.

The primary purpose of the spash screen is to inform the user as quickly as possible that the installer is starting up - it should appear about 200 to 500 msec after the installer is started.

A progess indicator should be a part of the splash screen if it will take more than 10 seconds to ready the installer for input from the user. While not strictly necessary, messages about the installer's activities during startup could be posted adjacent to the progress indicator. Such messages should be relvant to user-sensible activities, e.g. "Checking hardware", and remain visible for 3 to 8 seconds before changing.

The Splash screen should remain visible until just prior to the appearance of the Welcome screen. There should be a short break of 200 to 500 msec between the disappearance of the Splash and the appearance of the Welcome screen.

Welcome

The Wecome screen informs the user of the software to be installed, provides access to relevant documentation, and asks the user the type of task to be performed: install, upgrade, etc. [S] If the user selects "Install" the user can also choose the gross level of software to be installed: This CD, Full Desktop w/ developer tools, Server w/ Desktop, Server only, Minimal.

Defaults
  1. [S] There is no default task choice.
  2. [S] The Upgrade action will be disabled, with an explanatory note, until such time as Upgrade is supported by the installer.
  3. [S] The default software load is Full Desktop w/ developer tools
Behaviors
  1. The software choices are displayed only after the user clicks "Install"
Errors
  1. There are no error conditions

Disks: Install

This version of the Disks page appears when the user elects "Install" on the Welcome screen. It displays a list of attached disks which could reasonably be targets for installing Solaris. This includes not only internal disks but also external disks attached via external ports and non-traditional "disks" such as thumb drives and other types of storage cards.

Defaults
  1. If there is only one suitable installation (non-error emblemed) target disk, it should be selected by default
  2. x86 Only: When the user selects a suitable disk and Whole disk/Partition is displayed, Whole disk is the default.
Behaviors
  1. Icons for all potential targets will be displayed even if they are not suitable in some way. Unsuitable targets will be marked with a warning or error emblem as appropriate. There are different icons for removeable and non-removable media.
  2. While the mouse point is over a disk icon, additional information about the disk that can be read from the disk's prom, e.g. manfacturer name, model, etc., is displayed in a tooltip centered over the top 1/3 of the disk icon.
  3. Only one installation target/disk can be selected. When selected, the primary warning/error condition, if any,is displayed centered, to the extent possible, below the selected disk. The warnings/error conditions are listed below.
  4. When the first disk is selected, the "Whole disk/partitions..." text is displayed (provided the first disk does not have an "error" emblem.
  5. When a subsequent disk is selected, the "Whole disk/parttiions..." text is altered appropriately to reflect the newly selected disk. If the selected disk has an error emblem the partion information, if any is hidden and the "Whole disk/Partitions radio buttons are disabled.
  6. Partitioning behaviors:
    1. Partitioning is only possible with x86 systems. SPARC systems do not display the Whole disk/Partition choice.
    2. The disk partitions are not displayed to the user until they explicitly choose Partition. The existing partitions are then displayed.
    3. The partitions are always displayed in block order beginning with block zero in order to make the side effects of size change more predictable.
    4. Four partitions are always displayed even if fewer have been defined. This makes it easy for the user to create a new partition.
    5. Extended fdisk partitions are not supported though their existance and size must be displayed.
    6. Data in existing partitions should be preserved if possible. Any partition whose data will be destroyed should be so marked.
    7. Changing the type and/or size of an existing partition will cause its data to be destroyed. Changing the size of one partition will likely force subsequent partitions to be destroyed and recreated at new block addresses, causing their data to also be destroyed.
    8. If a partition's size is set to zero, its type should be changed to "Unused." It doesn't make sense to have a zero sized partition.
    9. A read-only "Unallocated" field will track any disk space that has not been allocated to a specific partition. It can take a negative value if the user temporarily overallocates the disk space.
    10. Typing "=" into a partition size will alter its size such that the Unallocated space will go to zero. This makes it easy for the user to allocate all disk space.
    11. The user can temporarily create mulitple Solaris partitions and/or overallocate disk space creating apparent error situations. This is allowed to make it easier for the user to redefine that disk partitioning.
    12. Errors and warning are reported when the user clicks the Next button. Only the highest priority error/warning will be reported - it is less confusing and the user may incidentally fix (or create) additional errors/warnings while addressing the reported error. The priority is: One Solaris partitions, overallocated diskspace, target is smaller than recommended size. The screen will not advance until all errors have been corrected. A user can advance in the face of warnings.
Errors
  1. When selecting a disk:
    1. Disk too small for installation: "This disk is too small."
  2. When clicking "Next": (Check in the following order after first.)
    1. If no disk has been selected: "Select a disk for installation"
    2. The selected disk has an Error tag: "The selected disk cannot be used<p>Select another disk."
    3. If there are two or more Solaris partitions: "There must be only one Solaris partition"
    4. If there are no Soalris partitions: "There must be one Solaris partition"
    5. The space allocated exceeds the size of the disk. "The disk space has been overallocated<p>Reduce the size of one or more partitions until the available space is zero."
    6. The selected partition has less than the absolute minimum disk space need for installation: "The Solaris partition is too small for installation"
Warnings
  1. When selecting "Partitions":
    1. If the disk has not been previously partitioned, or if the partition table is not recognizable, e.g. a GPT format: "The whole disk must be partitioned. Unrecognized partition table." A suggested partitioning is displayed - one Solaris partition for the whole disk.
  2. When altering the size of an existing partition:
    1. The data on the resized partition will be destroyed:  "image/dialog-warning.png  Warning: the data on this partition will be erased."
    2. If resizing a partition forces subsequent partitions to be moved a warning should appear next to each of the moved partitions:  "image/dialog-warning.png  Warning: the data on this partition will be erased."
  3. When clicking Next: (Check after all error conditions have been tested and cleared.)
    1. The disk is smaller than the recommended size, but is larger than the known absolute minimum: "The selected disk is smaller than the recommended minimum size<p>You may have difficulty installing and running some applications."
    2. The Solaris partition is smaller than the recommended size, but is larger than the known absolute minimum: "The Solaris partition is smaller than the recommended minimum size<p>You may have difficulty installing and running some applications."
    3. If gaps prevent allocating all the space to a partition as requested by a user: "Disk partitions are smaller than requested<p>The available disk space was not contiguous. Either set unneded partitions to "Unused" or use a third party partitioning application."
For the Future
  • Requests
    1. [S] A mechanism so that the user can refresh the disk list after inserting a removable media or adding/turning on an external disk drive - a rescan button. (Dave)
    2. [S] Recognize and deal with multiple Solaris fdisk partitions. This in not a supported configuration, but it can be created. (Ethan)
    3. The error/warning message displayed when a disk is selected should be centered under the disk and scroll with the icon when the disk list is scrolled. (Frank)
    4. [S] Inform the user that a Solaris environment exists on a disk (Tribble)

Disks: Upgrade

This version of the target selection page appears when the user elects to Upgrade an existing Solaris installation. The screen displays all Solaris installations and allows the user to select the one to be upgraded

Defaults
  1. If there is only one suitable upgrade target, it is selected by default.
Behaviors
  1. All Solaris installations should be displayed even if they are not suitable for upgrade. Unsuitable targets will be disabled. The reason for a taget's unsuitability will be indicated as part the target information:
     Solaris version too old
     Insufficient available space
     SVM volume
  2. Disks w/o any Solaris environments should be displayed. The following message should appear in the location that normally displays the first Solaris environment: information No Solaris environments.
  3. While the mouse point is over a disk icon, additional information about the disk that can be read from the disk's prom, e.g. manfacturer name, model, etc., is displayed in a tooltip centered over the top 1/3 of the disk icon.
  4. Only one Solaris environment can be selected.
  5. The installer should display as much usable information about each environment as is feasible in order tha the user can unabiguously identify the intended target: Solaris version, environment size, parent disk, etc. The precise information is TBD.
  6. [S] When Next is clicked, if there are no errors or warnings and there is less than a designated free space in the partition, a complex check is required to insure there is enough room for the update. Continue to display the current Disks (upgrade) screen and post an information dialog with the following message:
     Checking available disk space.
     This will take several minutes.
     [async progress bar]
     (Cancel) - if this test can be aborted, otherwise no button. Aborting the test removes the dialog and leaves the Disk (upgrade) screen unchanged, as if the user had not clicked Next.
     When the test completes, remove the dialog. If the space check succeeds proceed to the next screen (update summary). If the test fails post a new failure dialog with the following message:
     Insufficient disk space.
     The selected Solaris environment cannot be upgraded.
     (Close)
     When the user clicks Close, the dialog is removed and the Disk (upgrade) screen remains unchanged. Leave the Solaris instance selected so that the user knows which instance he was trying to upgrade.
Errors
  1. When Next is clicked: one Solaris environment must be selected: "Select the Solaris environment to be upgraded."
  2. If there are no upgradeable Solaris environments a confirmation style dialog should automatically be displayed as soon after the Disk (upgrade) screen is displayed:
     No upgradeable Solaris Environments
     Would you like to install?
     (Cancel)(OK)
     If the user clicks OK, remove the dialog and display the Disks (install) screen; if Cancel, remove the dialog and remain on the Disks (upgrade) screen.
For the Future
  • Requests
    1. [S] A mechanism so that the user can refresh the disk list after inserting a removable media or adding/turning on an external disk drive. (Dave)
    2. [S] Sort the solaris environments on a disk so that the non-upgradeable ones are after the upgradeable ones. Remove the radio buttons from the ones that are not upgradeable. (UIRB TCA 5.3)
    3. [S] Replace the disk icons with standard disk icons in order to be theme compatible. (Accessibility)

Time Zone, Date and Time

This screen enables the user to configure the computer's internal clock.

Defaults
  1. The date and time should be defaulted from either the computer's current clock values or, if not available, from the network if possible.
  2. The time zone and daylight savings time setting should be defaulted from the computer's internals settings or the network if either are available.
Behavior
  1. The user sets the timezone either by choosing from the region, country, and time zone drop-downs.
  2. Only the Region time zone is initially enabled - the country and time zone drop-downs initially have no values so they shouldn't be enabled.
  3. Selecting a region value fills the country drop-down with the corresponding values and enables the drop-down. Time zone has no values and is disabled.
  4. Selecting a country fills the time zone with the corresponding values and enables it. If there is only one time zone for the selected country the time zone value is set to "(single time zone)" and remains disabled.
Errors
  1. When the user clicks Next:
    1. The timezone must be set: "Time zone not specified\nSet your time zone using the Region, Country, and Time zone controls."
    2. The date must be valid: "The date setting is invalid.<p>Please set the date to today's YYYY/MM/DD."
    3. The time must be valid: "The time setting is invalid.<p>Please set the current time."
For the Future
  1. [S] Add a map for setting timezone.
    1. The user can set the timezone either by clicking a city on the map (future release).
    2. Target cities on the map should "light" when the mouse moves over the map. This will help a user to locate targets.
    3. When the mouse pointer is over a city, a tooltip should indicate the city name.
    4. Clicking a city should automatically set the region, country, and timezone drop-downs.
  2. [S] Set defaults from the network
  3. Add a mechanism to simplify navigating the country drop-down (UIRB TCA 5.2) Note: page-up/-down speed navigation. The suggested type-ahead mechanisms should be implemented in the toolset controls themselves. We might do the implementation and offer back to the community.

Languages

This screen is used to set the language support to be installed and the language support in effect when the system reboots after installation. This has the side-effect of establishing the system language translations to be installed and the translations to be used when the system boots.

Historically Solaris presented the user with languages, locales, and charactersets. This has been quite confusing and lead to non-sequitors, e.g. a geography based language list. The listing of multile charactersets for a given language has also been quite confusing. xDesign has worked with the Sun Globablization team to develop a different approach, one that turns out to be quite similar to the approach that has been used with some of the Linux distributions. The initial fruit of this effort is visible in the Login/Options/Languages list in Nevada build 56. The Caiman installer UI is consistent with this direction.

Defaults
  1. The Languages list will initially have one or more languages selected based on:
    1. The installer language
    2. The languages used within the previously selected timezone/country
    3. The keyboard type
  2. The Primary Language will default based on timezone/country. If more than one language is used within the timezone/country, the one matching the installer language will be selected.
  3. The system translation to be installed will default as follows: Primary Language, installer language, English
Behaviors
  1. The user can select all, none, one, or multiple language support to be installed.
  2. The Primary Language drop-down will list all the language/country pairs for all of the languages selected in the languages list.
  3. If the current primary language is deselected in the language list, the current primary language is set to POSIX/C
  4. The Select All button selects all language list entries. The primarly language drop-down is unaffected.
  5. The Deselect All button unchecks all language list entries and sets the Primary Language to POSIX/C.
  6. The Reset button resets the language list and primary language drop-downs to their initial default states.
Errors
  1. None

Users

The Users screen enables the user to set the root password and to create a user account that will be available at login.

Defaults
  1. The "Host name" field is defaulted to "solaris-devx".
Behaviors
  1. When a user tabs into a field, the entire content of the field is automatically selected. These simplifies replacing a field's current content. However, if a user sets focus by mouse clicking in a field the insertion point should be set.
  2. The user is not required to create a root password.
  3. The user is not required to create a user account. A user account requires only a Login name to be valid.
  4. The Computer name field initially displays a common default value, solaris-devx.
  5. There is no password "complexity" checking.
  6. During password entry the cursor advances but only an expanding, contiguous grey or blank field is is visible.
  7. Several fields, as noted under errors below, are checked for validity when they lose focus. If invalid, an error is posted next to the field. The field is not cleared as the user may not immediately notice the error message and a cleared field may not be caught when Next is clicked. When the user enters a valid value into the field, the error message is cleared and the default informational message, if any, is restored.
  8. When the user clicks Next and an error dialog is displayed, when the user dismisses the dialog, focus is automatically given to that field and its content is selected. The same applies to a warning dialog if the user clicks Cancel.
Errors
  1. The "re-typed" password is compared with the initial entry when the re-entry field loses focus. If they do not match a failure message is posted next to the re-typed password and both password fields are cleared. The focus is not reset to the password field as the user may not be looking at the screen. When a value is re-entered into the first password field is re-entered and the field loses focus, reset the error message on the re-enter password field to its default string: "Re-enter..."
    1* image/error-12x12.png Error: Passwords do not match
  2. The Login name field is checked for "root" when the field loses focus. If found, the Login name field is cleared and the following error message is displayed next to the field. The focus is not reset to the login field as the user may not be looking at the screen.
    1. image/error-12x12.png Error: "Root" cannot be used.
  3. When the host name field loses focus it is checked. If the field is blank, value is reset to the default and the following error message is displayed next to the field
    1* image/error-12x12.png Error: A host name is required.
  4. When Next is clicked:
    1* It will be common for someone to enter only a root password and hit Next or to enter all fields (and accept the host name default). In both cases there hasn't been a defocus on the password field so the user doesn't get a proper warning of the password verification failure. Do the following checks in order. Do not proceed beyond the first failure, i.e. only one error message at a time.
    1* Verify the root passwords match and put up an error dialog if they don't.
    1  "Root Password Invalid <p> The two root passwords do not match.\nRe-enter the root password."
    1* Verify the user password match and put up an error message if they don't match.
    1     "User Password Invalid<p> The two user passwords do not match.\nRe-enter the user password."
    1* Verify the Login name is not "root".
    1 "Invalid User Account <p> "Root" is not a valid Login name.\nEnter a different Login name."
    1* Verify the user account has a Log-in name if any other user account fields are non-blank.
    1     "Invalid User Account <p> The Log-in name cannot be blank.\nEnter a Login name or clear all user account fields."
Warnings

When Next is clicked, after all error checks are completed:

  • The user is warned if the root password is not defined or if the user account information is improperly defined (only a Login name is required).
    • "No root password<p>A root password had not been defined. The system is completely unsecured.\nClick Cancel to set a root password."
  • The computer name field cannot be blank - the user may have cleared the default value but did not enter a new value. Reset the computer name field to the default value.
    • "Invalid computer name" <p> The computer name cannot be blank. It has been reset to the default value.\nClick Cancel to set a different computer name."
For the Future
  • Requested:
    1. [S] Disable "pasting" into password fields (UIRB TCA 5.5)

Install/Upgrade Confirmation

This screen lists information provided by the user during the earlier screens:

  • The screen title reflects the selected operation: Install/Upgrade
  • The disk and, if specified, partition target information (install) or disk and solaris instance information (upgrade)
  • The version of Solaris, desktop, and specific tools to be installed/upgraded and the size of the software to be installed, including language support and translations.
  • If installing:
    • Language support and primary language
    • Timezone, but not date and time
    • User: root only if "No root password" warning; user account name or "No user account" warning; computer name
Defaults
  1. None
Behaviors
  1. None
Errors
  1. None
For the Future
  • Requested:
    1. Move screens that can be defaulted to tabs in the summary screen. Report defaults in the summary. (Frank)
    2. Section headers in summary are links to the screen/tab used to set the values in that section. (Frank)

Install/Upgrade Progress

The progress screen informs the user of approximate progress of the installation. All software is installed while this page is visible. It also displays targeted tecnical and marketing messages that appear while the installation proceeds. The messages are "canned", i.e. they are on the install disk. Future versions of Caiman may be able to access these message from the network and link to pages in various Sun websites.

Defaults
  1. None
Behaviors
  1. User-level status messages above the progress bar are updated no more frequently than two seconds. They may remain much longer. There should be no "Installing package x" type messages that flash rapidly.
  2. The progress bar should display and update a completion percenge number that reflects the current length of the progress bar.
  3. The technial/marketing messages should appear for at least 60 seconds, long enough to comfortably read and understand the message and to copy down any links. Placing the mouse over the message prevents the message from changing. The left/right cursor keys can return/advance through the messages.
  4. The Quit button is disabled.
  5. If the Solaris install/upgrade fails, go to the Installation/Upgrade Failed screen.
  6. If the Solaris install/upgrade succeeds, go to the Finished screen.
Errors
  1. If Solaris fails to install/upgrade, proceed to the Install/Upgrade Failed screen.
Warnings
  1. None.
For the Future
  • Requests for consideration
    1. Some form of fine-grained feedback to the user can know that the install isn't locked-up. (Moinak)
    2. A scrolling list of packages being installed for fine-grained feedback. (Moinak)
    3. Align the content of the marketing messages with the content of the Developer Guide. (UIRB TCA 5.7)
    4. Consider showing more detailed installation progress information, e.g. package names and estimated time to completion. This info might be hidden by default. (UIRB TCA 5.8)

Finished

The Finished screen informs the user of the successful completion of the Solaris installation/upgrade. (If Solaris failed to install/upgrade properly the Failed screen is displayed.) Subsequent paragraphs inform the user of the success of failure of additional software that was installed, e.g. the tools, to the extent that their installation scripts provide information. Regardless of succeess/failure of the tools installation/upgrade, the Reboot button, in the Next button's location, is enabled.

Defaults
  1. None
Behaviors
  1. There are links to open windows that display the Solaris and tools installation logs.
  2. The Quit button does not request confirmation. A terminal window is automatically opened after the installer quites.
  3. Quitting should not close the installation log windows, if open.
Errors
  1. None

Install/Upgrade Failed

This page is displayed if the Solaris portion of the installation/upgrade fails. The user will have the opportunity to view the installation log or use a terminal window to determine the cause of failure.

Defaults
  1. None
Behaviors
  1. The user can click a "View Log" link to view the log in a separate window.
  2. The Quit button does not request confirmation. Quitting should not close the installation log windows, if open.
Errors
  1. None
Tags:
Created by admin on 2009/10/26 12:12
Last modified by admin on 2009/10/26 12:12

Collectives

Project caiman Pages

XWiki Enterprise 2.7.1.34853 - Documentation