Difference between revisions of "Features/Display section for control panel"
(Created page with ' <noinclude>{{TOCright}} Display section for Control Panel </noinclude> == Summary == This is an enhancement to the Control Panel that enables the section ...') |
m (moved Features/XrandrCPSection to Features/Display section for control panel: more descriptive title) |
(No difference)
|
Latest revision as of 15:37, 6 June 2010
Summary
This is an enhancement to the Control Panel that enables the section of an external display on non-OLPC XO hardware.
Owner
- Name: Walter Bender
- Email: <walter at sugarlabs dot org>
Current status
- Targeted release: (0.90)
- Last updated: (06 June 2010)
- Percentage of completion: 0%
This feature is being tracked in Ticket XXXX.
Benefit to Sugar
There are times when you would like to be able to attach a projector to your Sugar presentation. It would be convenient to be able to do this through the control panel rather than from the command line.
Scope
To implement this feature:
- a new icons were added to share/icons/sugar/scalable/devices:
- vga.svg
- a new section was added to sugar/extensions/cpsection
- display
- a new icon was added to sugar/data/icons
- module_display.svg
How To Test
Features/Display section for control panel/Testing
User Experience
When a projector is available, it is great to be able to take advantage of it. This will make it easy for a teacher unfamiliar with the command line and xrandr to enable VGA out.
Note that the section only will appear on non-XO hardware. There is no change to user experience with Sugar on XO platforms.
Dependencies
No additional dependencies are required to implement this feature.
Contingency Plan
None necessary, revert to previous release behavior.
Documentation
Release Notes
File:Display-control-panel-selection.png
The Sugar Release Notes inform end-users about what is new in the release. An Example is 0.84/Notes. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.