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.

Release Notes

Comments and Discussion

See Talk:Development Team/Buddy_Positioning

@@ Line 1: / Line 1: @@
-<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TOCright}}</noinclude>
+<noinclude>{{GoogleTrans-en}}{{TOCright}}
+[[Category:Feature|Buddy Positioning]]
+[[Category:Feature Accepted 0.88]]
+</noinclude>
-= Feature Name =
+= Buddy Positioning =
-Positioning
 == Summary ==
-Use buddy color to seed the position to get a more stable positioning in the mesh view.
+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: [[User:Erikos| Simon Schampijer]]
+* Email: simon AT sugarlabs DOT org
-''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''
-* email: simon AT sugarlabs DOT org
 == Current status ==
-* Targeted release: (SUGAR_VERSION)
+* Targeted release: 0.88
-* Last updated: (DATE)
+* Last updated: 14.08.09
-* Percentage of completion: XX%
+* Percentage of completion: 0%
 == Detailed Description ==
-''Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better.''
+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 [[What is Sugar?|Sugar]] ==
+== Benefit to Sugar ==
-''What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?-->
+This is a stabilizing feature to the collaboration experience. It can be used to visually debug a networking situation as well.
 == Scope ==
-''What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''
+This change will only affect the sugar shell.
 == 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.''
+* 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
-''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.''
+* restart Sugar, the position should be the same as well
-''A good "how to test" should answer these four questions:''
-* ''What special hardware / data / etc. is needed (if any)?
-* ''How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?
-* ''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?''
 == User Experience ==
-''If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice.''
+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 ==
-''What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the python?''
+The change is only in the sugar shell and does not affect other packages.
 == Contingency Plan ==
-''If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.''
+Will be deferred to [http://wiki.sugarlabs.org/go/Development_Team/Release/Roadmap/0.88 Sucrose 0.88].
 == Documentation ==
-''Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved.''
+Ticket [http://dev.sugarlabs.org/ticket/381 381] contains some more information.
 == Release Notes ==
-''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[DevelopmentTeam/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.''
+<!-- 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 ==
-* See See [[Talk:Development Team/Feature Template]] <!-- 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 [[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 with incomplete scope]]

Difference between revisions of "Features/Buddy Positioning"