Line 1: |
Line 1: |
− | <noinclude>{{TOCright}} | + | <noinclude> |
− | [[Category:Feature|SugarAdhocNetworks]] | + | [[Category:Feature Accepted 0.90]] |
| + | [[Category:FeatureLanded|Ad hoc Networking]] |
| </noinclude> | | </noinclude> |
| | | |
| == Summary == | | == Summary == |
− | The Feature will add three default Ad-hoc networks, for channel 1, 6 and 11. They will be represented with designated icons in the neighborhood view. | + | The Feature will add three default ad hoc networks, for channel 1, 6, and 11. They will be represented with designated icons in the Neighborhood view. |
| | | |
| == Owner == | | == Owner == |
Line 16: |
Line 17: |
| | | |
| == Detailed Description == | | == Detailed Description == |
− | The Feature will add three default Ad-hoc networks, for channel 1, 6 and 11. They will be represented with designated icons in the neighborhood view. This will mimic the mesh behavior on devices where mesh hardware is not available and make the "under a tree"-scenario possible in those cases. If Sugar sees no "known" network (the learner has not been connected to an currently available Access Point before) when it starts, it does autoconnect to an Ad-hoc network. First we try if there is an Ad-hoc network that is used by other learners in the area, if not we default to channel 1. | + | The Feature will add three default ad hoc networks, for channel 1, 6, and 11. They will be represented with designated icons in the Neighborhood view. This will mimic the mesh behavior on devices where mesh hardware is not available and make the "under a tree"-scenario possible in those cases. If Sugar sees no "known" network (the learner has not been connected to an currently available Access Point before) when it starts, it does autoconnect to an ad hoc network. First we try if there is an ad hoc network that is used by other learners in the area, if not we default to channel 1. |
| | | |
| == Benefit to Sugar == | | == Benefit to Sugar == |
− | The Feature will allow small groups of learners to collaborate without the need of an infrastructure, the so called "under a tree"-scenario more easily. In previous Sugar releases the learner could create an Ad-hoc network by using an option in the wireless device palette. This representation will be more accessible to the learners. | + | The Feature will allow small groups of learners to collaborate without the need of an infrastructure, the so called "under a tree"-scenario more easily. In previous Sugar releases the learner could create an ad hoc network by using an option in the wireless device palette. This representation will be more accessible to the learners. |
| | | |
| == Scope == | | == Scope == |
− | | + | The sugar module is affected by this Feature and the sugar-artwork module by the addition of the six icons (3 channels, two states each). The patch tries to not be too invasive as it is meant to be back ported to 0.84. |
| | | |
| ==UI Design== | | ==UI Design== |
− | The Ad-hoc networks are represented using [http://en.wikipedia.org/wiki/Maya_numerals Maya numerals]. They use the same representation as access points to show the status of the connection (picture one). The fill color is used to indicate if other members are connected to the network. It does not indicate the number of people that are connected though. If the fill color of the Ad-hoc icon is set then there is at least one person listening [[Features/Sugar_Adhoc_Networks/Testing#Members | (picture members)]]. | + | The ad hoc networks are represented using [http://en.wikipedia.org/wiki/Maya_numerals Maya numerals]. They use the same representation as access points to show the status of the connection [[Features/Ad hoc_Networking/Testing#Connect_both_machines_to_the_same_channel | (picture Connected)]]. The fill color is used to indicate if other members are connected to the network. It does not indicate the number of people that are connected though. If the fill color of the ad hoc icon is set then there is at least one person listening [[Features/Ad hoc_Networking/Testing#Members | (picture members)]]. |
| | | |
| == How To Test == | | == How To Test == |
Line 31: |
Line 32: |
| | | |
| == User Experience == | | == User Experience == |
− | No changes.
| + | The user experience should be similar to the one with mesh networks. With having the ability to indicate if a network has members there should even be an improvement to know which network (channel) one should connect to. |
| | | |
| == Dependencies == | | == Dependencies == |
− | Will add a dependency on [http://telepathy.freedesktop.org/wiki/Mission%20Control telepathy-mission-control] and will need updated versions of telepathy-gabble and telepathy-salut.
| + | There was an [http://mail.gnome.org/archives/networkmanager-list/2010-April/msg00127.html issue in NetworkManager] reporting not the correct channel for ad hoc networks. The patch has been landed to master and the [http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=NETWORKMANAGER_0_7 NETWORKMANAGER_0_7 branch]. Make sure you have at least NetworkManager-0.7.2.997-1. |
| | | |
| == Contingency Plan == | | == Contingency Plan == |
− | None necessary, revert to previous release behaviour. I will be able to invest time until the 0.90 release to fix any bugs that may be introduced by the Feature. | + | None necessary, revert to previous release behavior. I am available until the 0.90 release (and after) to fix any bugs that may be introduced by the Feature. |
| | | |
| == Documentation == | | == Documentation == |
| + | * [http://lists.laptop.org/pipermail/devel/2009-December/026831.html Initial discussion at OLPC.] |
| + | |
| + | * [http://lists.sugarlabs.org/archive/sugar-devel/2010-April/023584.html Design thread on sugar-devel.] |
| | | |
| + | * {{OlpcBug|9845}} {{Bug|1610}} |
| | | |
| == Release Notes == | | == Release Notes == |
− | TBW
| + | Still coming. |
| | | |
| == Comments and Discussion == | | == Comments and Discussion == |
| * See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- 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 [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- 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. --> |