Launchpad Entry: jaunty-ubiquity-usability
Packages affected: ubiquity, oem-config
Unimplemented usability tasks from previous specifications, as well as some new usability tasks, will make Ubiquity accessible to even more users.
Over time a number of usability issues have been discovered in ubiquity. Some of these were previously planned to be fixed, but time was not permitting. Other suggested fixes are new or are progressions from recently developed functionality.
TODO * Scott finds the timezone selection widget to be difficult to use.
Investigate porting the new language selector widget from oem-config's GTK frontend to ubiquity. Unlike oem-config's language page, most of the text on ubiquity's will need to remain, however some space might be found by getting the labels to expand properly.
Where are you?
Replace the timezone selector with the one proposed in UbiquityVisualRefresh and make sure that, unlike the previous iteratoration, it's placed in a frame.
Modify the "Selected city" menu to display time zone areas and branch out to individual time zones. This can be accomplished by developing Python bindings to GWeatherTimezoneMenu and using that, or porting the relevant code for pop-out menus to Python.
Radio buttons for "suggested option" and "choose your own" will be added to the keyboard selection page to ease the confusion of selecting a keyboard when there are many variants as originally part of HardyUbiquityUsability.
A "Calculate layout..." button will be added to the right of the keyboard layout test input box. This will match the functionality already found in debian-installer.
Prepare disk space (automatic partitioning)
The resize widget will be removed and functionality to replace it will be developed for the SegmentedBar widget that was developed for Intrepid.
A warning will be added to the "use entire disk" option that indicates what operating systems will be lost if the entire disk is formatted. Care will need to be taken to ensure that this string can be translated.
The "Guided" and "SCSI1 (0,0,0)" portions of the labels will be removed.
The labels on the SegmentedBars will read "Ubuntu 8.10 (/dev/sda5) \n 5% (3.0 GB)" instead of "/dev/sda5 \n 5%". The operating system titles will be sourced from os-prober, which will be moved into a function in misc.py that can be called in the other areas that it's needed.
Replacing the labels below each bar with a chart of the partitions, placed to the right of the option buttons, will be investigated as a solution to the problem of the labels expanding too far horizontally.
The colors used for partitions that exist in both SegmentedBars will be made to match.
Prepare partitions (manual partitioning)
The current code creates a number of SegmentedBars in the background. This is a waste of memory, and will be rewritten to match what the automatic partitioning page does.
Who are you?
A password strength meter will be added to the right of the password input boxes.
Migrate documents and settings
The migrate documents and settings page will not be shown if nothing can be imported.
Ready to install
Clickable page labels will be added. Clicking on one such label will take the user back to the page it refers to. Given the design of the components, it may be necessary to force the user to go back to the summary page after going back to a component page.
In order to accommodate this change, and to fix a long standing bug that requires the "Migration Assistant:" label to always be displayed, the summary question will be split into several questions by section.
File copy progress time remaining will be calculated and displayed in minutes, so the potential variation in time is less noticeable.
A slideshow will be added above the progress bar as described in UbiquityVisualRefresh.
BoF agenda and discussion
- Should we and how can we merge the automatic and manual partitioning pages? What would the UI for this look like?
- What should the password strength meter look like?
- Should we add the private directory option to the "Who are you?" page? What would the UI look like?
- Should we add an OpenID option?