Difference between revisions of "Features/Buddy Positioning"
| Line 25: | Line 25: | ||
== How To Test == | == How To Test == | ||
| − | + | * you need several machines running sugar (or several sugar-jhbuild instances) | |
| − | + | * run several instances, the buddy should be positioned the same on all the neighborhood views | |
| − | + | * restart Sugar, the position should be the same as well | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== User Experience == | == User Experience == | ||
Revision as of 03:56, 15 July 2009
Buddy Positioning
Summary
Use the identity of the neighborhood icons (color or nick name for the buddy) 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
- you need several machines running sugar (or several sugar-jhbuild instances)
- run several instances, the buddy should be positioned the same on all the neighborhood views
- restart Sugar, the position should be the same as well
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.