LanguageSelector
⇤ ← Revision 1 as of 2010-05-18 16:06:17
5029
Comment:
|
5101
|
Deletions are marked like this. | Additions are marked like this. |
Line 31: | Line 31: |
The following is an idea how the structure of the assistant could look like: | The following are ideas how the structure of the assistant could look like: Idea 1: |
Line 87: | Line 89: |
Idea 2: [[attachment:language-selector-maverick.glade]] |
Launchpad Entry: desktop-maverick-language-selector
Created:2010-05-18
Contributors: ArneGoetje
Packages affected: language-selector
Summary
As the current language-selector UI is a bit confusing for novice users, we want to create a walk-through assistant to make it easier to do those tasks.
Release Note
Rationale
As the current language-selector UI is a bit confusing for novice users, we want to create a walk-through assistant to make it easier to do those tasks. The current UI can then be reachable by clicking an 'Advanced...' button.
Use cases
- add or remove localization components for a given language or set of languages (language-packs, writing aids, fonts, input-methods)
- change the locale ("I'm based in this country/region") - does it make sense to set it system wide by default?
- change the language of the desktop ("I want my desktop to be shown in ...")
- change the system language of the login dialog (gdm)
Common use case to have the desktop translation in one language and add dictionaries or input methods for another language.
Design
- The label "Text" on the second tab should be reconsidered.
- Can we tell if its a single user vs multi user system, to provide better default actions?
- Hide actions that require root access if user does not have admin rights
The following are ideas how the structure of the assistant could look like:
Idea 1:
- Add/Remove language components (requires root permissions)
- display a list of installed language components
a) Language -> components:
├ English │ ├ Translations │ └ Dictionaries, word lists and spell checkers ├ Traditional Chinese │ ├ Translations │ ├ Additional fonts │ └ Input methods
b) Component -> languages:
├ Translations │ ├ English │ └ Traditional Chinese ├ Dictionaries, word lists and spell checkers │ └ English ├ Additional Fonts │ └ Traditional Chinese ├ Input Methods │ └ Traditional Chinese
- give the user the possibility to remove installed components (maybe except English translations? -- English is the default fall back if no other translation is available)
- have a '+' button to add new components
- a) add by language:
- choose target language
- select "everything" or by available component for that language
- select component
- add available languages for that component
- a) add by language:
- display a note that changes take effect with the next login.
- display a list of installed language components
- Change region settings (requires root permissions for system wide setting)
- select region of choice
- select language (if more than one is available)
- Change desktop language
- display a list of languages from the current setting (e.g. Frisian (Netherlands), Frisian, Dutch (Netherlands), Dutch, English (UK), English)
- display an alternative choice (recommended by language-selector)
- "customize" option:
- be able to remove entry from the above list
- be able to change the ordering of the above list
- a '+' button to add another language to the list
- Change login screen language (requires root permissions)
- display a list of languages from the current setting (e.g. Frisian (Netherlands), Frisian, Dutch (Netherlands), Dutch, English (UK), English)
- display an alternative choice (recommended by language-selector)
- "customize" option:
- be able to remove entry from the above list
- be able to change the ordering of the above list
- a '+' button to add another language to the list
Idea 2:
language-selector-maverick.glade
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
Unresolved issues
BoF agenda and discussion
The current widgets use both a tree and combo box for different tabs.
DesktopTeam/Specs/Maverick/LanguageSelector (last edited 2010-06-09 08:40:46 by www)