Difference between revisions of "Features/Replace combo box in language panel"

From Sugar Labs
Jump to: navigation, search
(Summary)
 
Line 1: Line 1:
 
<noinclude>
 
<noinclude>
[[Category:Feature|Replace combo box in language panel]]
+
[[Category:FeatureLanded|Replace combo box in language panel]]
 
</noinclude>
 
</noinclude>
  
Line 16: Line 16:
 
* Targeted release: 1.02
 
* Targeted release: 1.02
 
* Last updated: 2014-03-04
 
* Last updated: 2014-03-04
* Percentage of completion: 95% (patch written, awaiting further design review)
+
* Percentage of completion: 100%
  
 
See https://github.com/walterbender/sugar/tree/language-2
 
See https://github.com/walterbender/sugar/tree/language-2

Latest revision as of 07:25, 18 July 2014



Summary

The combo box on the language panel is unwieldy. This feature would replace the combo box with a pair of palettes: one for language and one for country.

Language-country.png

Owner

Current status

  • Targeted release: 1.02
  • Last updated: 2014-03-04
  • Percentage of completion: 100%

See https://github.com/walterbender/sugar/tree/language-2

Detailed Description

We ship lots of languages and country combos. The combo box on the language panel is unwieldy (and broken on touch -- it will not pop up properly on first touch). This feature would replace the combo box with two palettes (as shown in the figures).

From the palettes, you see more choices w/o needed to scroll. Plus the palettes are much easier to use with touch.

Benefit to Sugar

This feature will help us scale to more languages and give better touch support.

Scope

The intervention is limited to:

  • sugar/extensions/cpsection/language/view.py

How To Test

Features/Replace combo box in language panel/Testing

User Experience

The user will see two buttons and labels displayed instead of a combo box. In the examples illustrated, it means that rather searching through a long list in a combo box >10x the screen height, the user scans 2.5 screens of items.

Dependencies

No new dependencies

Contingency Plan

There is no adverse impact if this feature does not land.

Documentation

Release Notes

Comments and Discussion