Difference between revisions of "Features/Buddy Positioning"
| Line 25: | Line 25: | ||
== How To Test == | == How To Test == | ||
| − | + | <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.'' | |
''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.'' | ''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.'' | ||
| Line 35: | Line 35: | ||
* ''What specific actions do I perform to check that the feature is working like it's supposed to? | * ''What specific actions do I perform to check that the feature is working like it's supposed to? | ||
* ''What are the expected results of those actions?'' | * ''What are the expected results of those actions?'' | ||
| + | --> | ||
== User Experience == | == User Experience == | ||
| Line 53: | Line 54: | ||
== Comments and Discussion == | == Comments and Discussion == | ||
* See See [[Talk:Development Team/Buddy_Positioning]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | * See See [[Talk:Development Team/Buddy_Positioning]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | ||
| − | |||
| − | |||
[[Category:Feature]] | [[Category:Feature]] | ||
[[Category:Feature Page Incomplete]] | [[Category:Feature Page Incomplete]] | ||
[[Category:Feature Ready for Release Manager]] | [[Category:Feature Ready for Release Manager]] | ||
Revision as of 01:07, 15 July 2009
Buddy Positioning
Summary
Use the identity of the neighborhood icons (buddy color or nick name) to seed the position to get a more stable positioning in the neighborhood view.
Owner
- Name: Simon Schampijer
- Email: simon AT sugarlabs DOT org
Current status
- Targeted release: 0.86
- Last updated: 30.06.09
- Percentage of completion: 0%
Detailed Description
Ticket 381 contains some more information.
Benefit to Sugar
Right now the neighborhood view is disappointingly random from machine to machine, reboot to reboot, or even just over time as the view (seemingly randomly) refreshes. If the placement of the neighborhood icons is based on identity, the user can quickly learn where to expect resources to be spatially in the neighborhood view.
Scope
This change will only affect the sugar shell.
How To Test
User Experience
The user can quickly learn where to expect resources to be spatially in the neighborhood view. The positioning of the items in the neighborhood view should be constant between reboots, refreshes and different machines.
Dependencies
The change is only in the sugar shell and does not affect other packages.
Contingency Plan
Will be deferred to Sucrose 0.88.