Changes

<noinclude>

<noinclude>

[[Category:Feature Page Incomplete]]

[[Category:FeatureLanded|Network control panel]]

[[Category:Feature|Network control panel]]

</noinclude>

</noinclude>

== Summary ==

== Summary ==

The wireless control panel section is reworked to respect non-wireless connections.

The wireless control panel section is reworked and reworded to respect non-wireless connections.

''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''

The Wireless section is excluded when no wireless device is detected on the system.

== Owner ==

== Owner ==

== Current status ==

== Current status ==

* Targeted release: [[0.102]]

* Targeted release: [[0.102]]

* Last updated: 24 January 2014

* Last updated: 04 February 2014

* Percentage of completion: 80 %

* Percentage of completion: 100 %

== Detailed Description ==

== Detailed Description ==

The persistence of wireless connection configurations can lead to delays and unexpected auto-connections to networks that were once out-of-range.  A simple tool was provided to clear '''all connections''' (except the pre-defined Sugar [[olpc:Mesh_Network_Details|Mesh]] and [[wikipedia:GSM|GSM]] connections.

The persistence of wireless connection configurations can lead to delays and unexpected auto-connections to networks that were once out-of-range.  A simple tool was provided to clear '''all connections''' (except the pre-defined Sugar [[olpc:Mesh_Network_Details|Mesh]] and [[wikipedia:GSM|GSM]] connections.

This simple tool is welcome, but has proves to be too sweeping in its destruction of connections.  The code currently destroys all network configurations, regardless of their type.  So this is a problem for those using wired Ethernet (see bug {{bug|4410}}), Bluetooth, Mobile WiMAX, VLAN, or any of the other networking device types.

This simple tool is welcome, but has proved to be too sweeping in its destruction of connections.  The code currently destroys all network configurations, regardless of their type.  So this is a problem for those using wired Ethernet (see bug {{bug|4410}}), Bluetooth, Mobile WiMAX, VLAN, or any of the other networking device types.

Furthermore, the 'Discard network history' button, which triggers the connection destruction, is found in the 'Wireless' section of the control panel.

Furthermore, the 'Discard network history' button, which triggers the connection destruction, is found in the 'Wireless' section of the control panel.

== Benefit to Sugar ==

== Benefit to Sugar ==

The proposed reworking of this panel and code will avert trouble in the future as Sugar is deployed on new hardware with new connection types.  This is achieved by restricting the action of the 'Discard ...' button to non-Sugar wireless connections (both '802-11-wireless' and '802-11-olpc-mesh'). The supporting code is reworked to allow other groups of connections to be discarded, if needed, by new code in separate control panel sections.

The proposed reworking of this panel and code will avert trouble in the future as Sugar is deployed on new hardware with new connection types.  This is achieved by restricting the action of the 'Discard ...' button to non-Sugar wireless connections (both '802-11-wireless' and '802-11-olpc-mesh').

These changes advance Sugar's goal of providing a 'clear and simple' interface for learners.

These changes advance Sugar's goal of providing a 'clear and simple' interface for learners.

* {{Code|/usr/share/sugar/extensions/cpsection/network/view.py}}

* {{Code|/usr/share/sugar/extensions/cpsection/network/view.py}}

NetworkManager objects are used for all code paths except for the test for wireless hardware.

NetworkManager interfaces are used for all code paths, and while OLPC 13.2.0 uses NetworkManager 0.9.8.1-3.git20130514.fc18, which does not list wireless devices when the radio is disabled, the dependency on NetworkManager advances to version 0.9.9, which does.

: OLPC 13.2.0 uses NetworkManager 0.9.8.1-3.git20130514.fc18, which does not list wireless connections when the radio is disabled. The kernel API in the {{Code|/sys/module/cfg80211/holders/}} directory has been more stable.

 

To minimize the chances that a manually created connection (such as 'Sugar Ad-hoc Network 2') is falsely white-listed as one of the Sugar internal ad hoc or olpc-mesh connections, each connection is tested against a discrete white list and specific to the wireless mode or connection type.

Some corner cases in behavior have been ignored: If a custom GSM (or other non-wireless or non-mesh) connection had been created, they would no longer be discarded by the 'Discard ...' button.  These could not be created by the  graphical Sugar interface, so their creators are most likely capable of discarding them if needed.

Some corner cases in behavior have been ignored: If a custom GSM (or other non-wireless or non-mesh) connection had been created, they would no longer be discarded by the 'Discard ...' button.  These could not be created by the  graphical Sugar interface, so their creators are most likely capable of discarding them if needed.

==UI Design==

==UI Design==

* https://bugs.sugarlabs.org/ticket/4410

* https://bugs.sugarlabs.org/ticket/4410

* http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg36121.html

* http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg36121.html

* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

* See [[{{TALKPAGENAME}}|discussion tab for this feature]]