Difference between revisions of "Features/Buddy Positioning"
RafaelOrtiz (talk | contribs) |
|||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | <noinclude>{{ GoogleTrans-en | + | <noinclude>{{GoogleTrans-en}}{{TOCright}} |
| + | [[Category:Feature|Buddy Positioning]] | ||
| + | [[Category:Feature Accepted 0.88]] | ||
| + | </noinclude> | ||
= Buddy Positioning = | = Buddy Positioning = | ||
== Summary == | == Summary == | ||
| − | Use the identity of the neighborhood icons ( | + | Use the identity of the neighborhood icons (buddy unique keyid, or AP identity as per colour generating process) to seed the position to get a more stable positioning in the neighborhood view. |
== Owner == | == Owner == | ||
| Line 11: | Line 14: | ||
== Current status == | == Current status == | ||
| − | * Targeted release: 0. | + | * Targeted release: 0.88 |
| − | * Last updated: | + | * Last updated: 14.08.09 |
* Percentage of completion: 0% | * Percentage of completion: 0% | ||
| Line 42: | Line 45: | ||
== Release Notes == | == Release Notes == | ||
| − | <!-- The Sugar Release Notes inform end-users about what is new in the release. An Example is [[ | + | <!-- The Sugar Release Notes inform end-users about what is new in the release. An Example is [[Development Team/Release/Releases/Sucrose/0.84]]. 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. --> |
== Comments and Discussion == | == Comments and Discussion == | ||
| − | * | + | * 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 --> |
| − | |||
| − | |||
| − | |||
Latest revision as of 13:23, 25 November 2009
Buddy Positioning
Summary
Use the identity of the neighborhood icons (buddy unique keyid, or AP identity as per colour generating process) 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.88
- Last updated: 14.08.09
- Percentage of completion: 0%
Detailed Description
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.
Benefit to Sugar
This is a stabilizing feature to the collaboration experience. It can be used to visually debug a networking situation as well.
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.
Documentation
Ticket 381 contains some more information.