Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rework the wireless control panel section to respect non-wireless connec... #228

Closed
wants to merge 1 commit into from
Closed

Conversation

FGrose
Copy link
Contributor

@FGrose FGrose commented Jan 20, 2014

...tions

Fixes #4410 https://bugs.sugarlabs.org/ticket/4410

The 'Discard network history' button is peculiar to Sugar, and
is destructive to all non-wireless connections, despite being in
the 'Wireless' section of the control panel.

Relabel the code variables and functions to be specific to
wireless connections.

Recode the functions to exclude non-wireless connections.

Relabel the 'Radio' box instructions and 'Discard ...' button
to avoid confusion over their state and actions.

If wireless hardware is not present on the system, the 'Wireless'
section of the control panel is excluded.

The availability of wireless hardware is tested with the kernel's
sys filesystem because, with the radio disabled, wireless devices
are not exposed in the NetworkManager API and it would be
inappropriate to turn the radio on--just to see if one is present.

Wireless hardware present:
network-withwifi

No wireless hardware:
network-nowifi

…nections

Fixes #4410  https://bugs.sugarlabs.org/ticket/4410

The 'Discard network history' button is peculiar to Sugar, and
is destructive to all non-wireless connections, despite being in
the 'Wireless' section of the control panel.

Relabel the code variables and functions to be specific to
wireless connections.

Recode the functions to exclude non-wireless connections.

Relabel the 'Radio' box instructions and 'Discard ...' button
to avoid confusion over their state and actions.

If wireless hardware is not present on the system, the 'Wireless'
section of the control panel is excluded.

The availability of wireless hardware is tested with the kernel's
sys filesystem because, with the radio disabled, wireless devices
are not exposed in the NetworkManager API and it would be
inappropriate to turn the radio on--just to see if one is present.
@FGrose
Copy link
Contributor Author

FGrose commented Jan 20, 2014

[DESIGN] discussion thread started at http://lists.sugarlabs.org/archive/sugar-devel/2014-January/046900.html

@quozl
Copy link
Contributor

quozl commented Jan 20, 2014

Reviewed-by: James Cameron quozl@laptop.org

Like it.

@dnarvaez
Copy link
Contributor

Where are you testing this? In Fedora 20, the list of devices seems to be available even if wireless is disabled

[dnarvaez@vaio src]$ nmcli r
WIFI-HW  WIFI      WWAN-HW  WWAN    
enabled  disabled  enabled  enabled 
[dnarvaez@vaio src]$ nmcli d
DEVICE  TYPE      STATE       
wlp1s0  wifi      unavailable 
lo      loopback  unmanaged   

I have not tested with the dbus service directly, but I'd expect nmcli to ultimately be using the dbus service to get this info.

@dnarvaez
Copy link
Contributor

It seems like the code is handling adhoc networks specially, but I didn't find an explanation of that change. Can you please elaborate on it?

@dnarvaez
Copy link
Contributor

I'm finding a bit difficult to review this because there is a lot of code moving. I want to be extra careful here to not risk to regress something essential as wifi. I suggest that we split it up in two commits

1 Change the networks the button applies to.
2 HIde the section when wifi is not available.

@FGrose
Copy link
Contributor Author

FGrose commented Jan 22, 2014

Closing to divide and resubmit sequentially as discussed here,
http://lists.sugarlabs.org/archive/sugar-devel/2014-January/046939.html

@FGrose FGrose closed this Jan 22, 2014
@FGrose FGrose deleted the wireless-try4 branch January 22, 2014 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants